From: Ingo Oppermann via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Ingo Oppermann <ingo@datarhei.com>
Subject: Re: [FFmpeg-devel] FFmpeg 8.0 Name
Date: Wed, 20 Aug 2025 09:28:49 +0200
Message-ID: <63C18F2E-BA9F-4447-8674-ECA028FD49C0@datarhei.com> (raw)
In-Reply-To: <2499FB86-10CA-4769-A8EC-63FAFEA7CCF2@gmail.com>
> On 20 Aug 2025, at 00:27, Jacob Lifshay via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> wrote:
>
>
>
> On August 19, 2025 2:27:12 PM PDT, Michael Niedermayer via ffmpeg-devel <ffmpeg-devel@ffmpeg.org> wrote:
>> Hi all
>>
>> what name should we give 8.0 ?
>
> IDK if it's a very good suggestion, but Hachi? It's both the Japanese number 8, as well as a common nickname. There's a famously loyal dog with that name: https://en.wikipedia.org/wiki/Hachik%C5%8D
+1
>
> Jacob
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>
> To unsubscribe, visit link above, or email
> ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2025-08-20 7:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-19 21:27 Michael Niedermayer via ffmpeg-devel
2025-08-19 22:27 ` Jacob Lifshay via ffmpeg-devel
2025-08-20 7:28 ` Ingo Oppermann via ffmpeg-devel [this message]
2025-08-20 9:47 ` Frank Plowman via ffmpeg-devel
2025-08-20 9:54 ` Frank Plowman via ffmpeg-devel
2025-08-20 10:02 ` Gyan Doshi via ffmpeg-devel
2025-08-20 10:33 ` Reto Kromer via ffmpeg-devel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=63C18F2E-BA9F-4447-8674-ECA028FD49C0@datarhei.com \
--to=ffmpeg-devel@ffmpeg.org \
--cc=ingo@datarhei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git