From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] FFmpeg 4.4.6 and 4.2.11
Date: Sat, 15 Mar 2025 01:36:59 +0100
Message-ID: <20250315003659.GP4991@pb2> (raw)
In-Reply-To: <20250312131732.GX4991@pb2>
[-- Attachment #1.1: Type: text/plain, Size: 882 bytes --]
On Wed, Mar 12, 2025 at 02:17:32PM +0100, Michael Niedermayer wrote:
> On Mon, Mar 03, 2025 at 02:10:49AM +0100, Michael Niedermayer wrote:
> > Hi all
> >
> > As ive already backported and somewhat tested release/4.3 i intend to
> > make the next point release from that and after that next is
> > 3.4 (because its the supported branch that is longest without a release)
> >
> > like always, please backport things if you want something backported
> > please test, if you want something tested
> > and tell me if theres anything i need to know (like waiting for something)
>
> 4.3.9 released, 3.4.14 is next
3.4.14 released a few days ago too
next is 4.4.6 and 4.2.11
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Republics decline into democracies and democracies degenerate into
despotisms. -- Aristotle
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
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".
prev parent reply other threads:[~2025-03-15 0:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 1:10 [FFmpeg-devel] FFmpeg 4.3.9 and 3.4.14 Michael Niedermayer
2025-03-12 13:17 ` Michael Niedermayer
2025-03-15 0:36 ` Michael Niedermayer [this message]
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=20250315003659.GP4991@pb2 \
--to=michael@niedermayer.cc \
--cc=ffmpeg-devel@ffmpeg.org \
/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