From: Marton Balint <cus@passwd.hu>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Andreas Schneider <asn@cryptomilk.org>
Subject: Re: [FFmpeg-devel] FFmpeg 5.1
Date: Sun, 19 Jun 2022 22:59:28 +0200 (CEST)
Message-ID: <d7361cc-9355-888-475-acb51e6856b@passwd.hu> (raw)
In-Reply-To: <CAEg-Je8xUzOPHqzELfQLq4sSWc015Fvbfy6f4svhbwx+NDy8jg@mail.gmail.com>
On Thu, 9 Jun 2022, Neal Gompa wrote:
> On Tue, Jun 7, 2022 at 7:35 AM Michael Niedermayer
> <michael@niedermayer.cc> wrote:
>>
>> Hi all
>>
>> As was discussed previously the 5.1 release should be in june/july
>> That means in the next weeks probably!
>> If you know of any regressions, security issues or other major bugs,
>> please help fixing them
>>
>> Also as was suggested before, this release will get the "LTS" tag
>> unless people feel thats a bad idea of course
>>
>
> There were a few fixes we have in Fedora on top of 5.0 that would be
> nice to have in upstream 5.1:
>
> * http://ffmpeg.org/pipermail/ffmpeg-devel/2022-February/292877.html
> * http://ffmpeg.org/pipermail/ffmpeg-devel/2022-February/292853.html
> * http://ffmpeg.org/pipermail/ffmpeg-devel/2022-February/293194.html
>
> Would it be possible to make sure these are in?
>
These are already merged, except the last patch, which needs some further
explanaition if this is cosmetic change or actually changes some behaviour
(other than the possible user facing error message)
Regards,
Marton
_______________________________________________
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:[~2022-06-19 20:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 11:35 Michael Niedermayer
2022-06-09 18:13 ` Neal Gompa
2022-06-19 20:59 ` Marton Balint [this message]
2022-06-20 0:22 ` Neal Gompa
2022-07-07 22:52 ` Marton Balint
2022-07-07 20:47 ` Michael Niedermayer
2022-07-07 20:51 ` Timo Rothenpieler
2022-07-07 20:54 ` James Almer
2022-07-08 10:17 ` Timo Rothenpieler
2022-07-08 10:23 ` Timo Rothenpieler
2022-07-08 11:49 ` James Almer
2022-07-08 8:36 ` Jean-Baptiste Kempf
2022-07-08 8:52 ` Paul B Mahol
2022-07-08 13:52 ` Michael Niedermayer
2022-07-08 14:54 ` Leo Izen
2022-07-09 17:17 ` Andreas Rheinhardt
2022-07-21 17:09 ` Michael Niedermayer
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=d7361cc-9355-888-475-acb51e6856b@passwd.hu \
--to=cus@passwd.hu \
--cc=asn@cryptomilk.org \
--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