* [FFmpeg-devel] FFmpeg 5.0.1
@ 2022-03-28 23:31 Michael Niedermayer
2022-03-28 23:40 ` Diederick C. Niehorster
2022-03-29 15:23 ` Oneric
0 siblings, 2 replies; 6+ messages in thread
From: Michael Niedermayer @ 2022-03-28 23:31 UTC (permalink / raw)
To: FFmpeg development discussions and patches
[-- Attachment #1.1: Type: text/plain, Size: 548 bytes --]
Hi all
I intend to do a 5.0.1 release from the release/5.0 branch in the next days
as its high time to make a new release with all the bugfixes
so if you want to backport something please do so
thx
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Old school: Use the lowest level language in which you can solve the problem
conveniently.
New school: Use the highest level language in which the latest supercomputer
can solve the problem without the user falling asleep waiting.
[-- 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".
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [FFmpeg-devel] FFmpeg 5.0.1
2022-03-28 23:31 [FFmpeg-devel] FFmpeg 5.0.1 Michael Niedermayer
@ 2022-03-28 23:40 ` Diederick C. Niehorster
2022-03-29 21:08 ` Michael Niedermayer
2022-03-29 15:23 ` Oneric
1 sibling, 1 reply; 6+ messages in thread
From: Diederick C. Niehorster @ 2022-03-28 23:40 UTC (permalink / raw)
To: FFmpeg development discussions and patches
[-- Attachment #1: Type: text/plain, Size: 427 bytes --]
Hi Michael,
On Tue, Mar 29, 2022 at 1:31 AM Michael Niedermayer
<michael@niedermayer.cc> wrote:
>
> Hi all
>
> I intend to do a 5.0.1 release from the release/5.0 branch in the next days
> as its high time to make a new release with all the bugfixes
> so if you want to backport something please do so
Could you include the attached patch (not in master yet either) as it
fixes a regression in 5.0.0?
Cheers and thanks,
Dee
[-- Attachment #2: v5-0001-avdevice-dshow-fix-regression.patch --]
[-- Type: application/octet-stream, Size: 2037 bytes --]
[-- Attachment #3: 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".
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [FFmpeg-devel] FFmpeg 5.0.1
2022-03-28 23:31 [FFmpeg-devel] FFmpeg 5.0.1 Michael Niedermayer
2022-03-28 23:40 ` Diederick C. Niehorster
@ 2022-03-29 15:23 ` Oneric
1 sibling, 0 replies; 6+ messages in thread
From: Oneric @ 2022-03-29 15:23 UTC (permalink / raw)
To: FFmpeg development discussions and patches
On Tue, Mar 29, 2022 at 01:31:02 +0200, Michael Niedermayer wrote:
> I intend to do a 5.0.1 release from the release/5.0 branch in the next days
> as its high time to make a new release with all the bugfixes
> so if you want to backport something please do so
How about the recent fix for vf_subtitles 66901ce16271d1e36726af53f35cb5cd88b0b773:
https://patchwork.ffmpeg.org/project/ffmpeg/patch/20220314190638.24816-1-oneric@oneric.de/
Is it eligible for backporting?
Backporting to 5.0 should be a straightforward cherry-pick, for
backporting to 4.x see the patch from the following message instead:
https://ffmpeg.org/pipermail/ffmpeg-devel/2022-March/294513.html
_______________________________________________
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".
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [FFmpeg-devel] FFmpeg 5.0.1
2022-03-28 23:40 ` Diederick C. Niehorster
@ 2022-03-29 21:08 ` Michael Niedermayer
2022-03-29 21:12 ` Diederick C. Niehorster
0 siblings, 1 reply; 6+ messages in thread
From: Michael Niedermayer @ 2022-03-29 21:08 UTC (permalink / raw)
To: FFmpeg development discussions and patches
[-- Attachment #1.1: Type: text/plain, Size: 753 bytes --]
On Tue, Mar 29, 2022 at 01:40:26AM +0200, Diederick C. Niehorster wrote:
> Hi Michael,
>
> On Tue, Mar 29, 2022 at 1:31 AM Michael Niedermayer
> <michael@niedermayer.cc> wrote:
> >
> > Hi all
> >
> > I intend to do a 5.0.1 release from the release/5.0 branch in the next days
> > as its high time to make a new release with all the bugfixes
> > so if you want to backport something please do so
>
> Could you include the attached patch (not in master yet either) as it
> fixes a regression in 5.0.0?
it should be in master first, bypassing master is a bad idea
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Democracy is the form of government in which you can choose your dictator
[-- 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".
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [FFmpeg-devel] FFmpeg 5.0.1
2022-03-29 21:08 ` Michael Niedermayer
@ 2022-03-29 21:12 ` Diederick C. Niehorster
2022-03-29 21:21 ` Michael Niedermayer
0 siblings, 1 reply; 6+ messages in thread
From: Diederick C. Niehorster @ 2022-03-29 21:12 UTC (permalink / raw)
To: FFmpeg development discussions and patches
Hi Michael,
On Tue, Mar 29, 2022 at 11:08 PM Michael Niedermayer
<michael@niedermayer.cc> wrote:
>
> On Tue, Mar 29, 2022 at 01:40:26AM +0200, Diederick C. Niehorster wrote:
> > Hi Michael,
> >
> > On Tue, Mar 29, 2022 at 1:31 AM Michael Niedermayer
> > <michael@niedermayer.cc> wrote:
> > >
> > > Hi all
> > >
> > > I intend to do a 5.0.1 release from the release/5.0 branch in the next days
> > > as its high time to make a new release with all the bugfixes
> > > so if you want to backport something please do so
> >
> > Could you include the attached patch (not in master yet either) as it
> > fixes a regression in 5.0.0?
>
> it should be in master first, bypassing master is a bad idea
Agreed. The whole patch series was LGTMed by the dshow maintainer in
https://ffmpeg.org/pipermail/ffmpeg-devel/2022-March/294681.html, but
i think all but the attached patch need more discussion first. Since
this fixes a regression, could you (or someone on list) apply it to
master and backport it? I do not have commit rights.
Thanks!
Dee
_______________________________________________
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".
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [FFmpeg-devel] FFmpeg 5.0.1
2022-03-29 21:12 ` Diederick C. Niehorster
@ 2022-03-29 21:21 ` Michael Niedermayer
0 siblings, 0 replies; 6+ messages in thread
From: Michael Niedermayer @ 2022-03-29 21:21 UTC (permalink / raw)
To: FFmpeg development discussions and patches
[-- Attachment #1.1: Type: text/plain, Size: 1366 bytes --]
On Tue, Mar 29, 2022 at 11:12:47PM +0200, Diederick C. Niehorster wrote:
> Hi Michael,
>
> On Tue, Mar 29, 2022 at 11:08 PM Michael Niedermayer
> <michael@niedermayer.cc> wrote:
> >
> > On Tue, Mar 29, 2022 at 01:40:26AM +0200, Diederick C. Niehorster wrote:
> > > Hi Michael,
> > >
> > > On Tue, Mar 29, 2022 at 1:31 AM Michael Niedermayer
> > > <michael@niedermayer.cc> wrote:
> > > >
> > > > Hi all
> > > >
> > > > I intend to do a 5.0.1 release from the release/5.0 branch in the next days
> > > > as its high time to make a new release with all the bugfixes
> > > > so if you want to backport something please do so
> > >
> > > Could you include the attached patch (not in master yet either) as it
> > > fixes a regression in 5.0.0?
> >
> > it should be in master first, bypassing master is a bad idea
>
> Agreed. The whole patch series was LGTMed by the dshow maintainer in
> https://ffmpeg.org/pipermail/ffmpeg-devel/2022-March/294681.html, but
> i think all but the attached patch need more discussion first. Since
> this fixes a regression, could you (or someone on list) apply it to
> master and backport it? I do not have commit rights.
ill apply it
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Never trust a computer, one day, it may think you are the virus. -- Compn
[-- 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".
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2022-03-29 21:21 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-03-28 23:31 [FFmpeg-devel] FFmpeg 5.0.1 Michael Niedermayer
2022-03-28 23:40 ` Diederick C. Niehorster
2022-03-29 21:08 ` Michael Niedermayer
2022-03-29 21:12 ` Diederick C. Niehorster
2022-03-29 21:21 ` Michael Niedermayer
2022-03-29 15:23 ` Oneric
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