From: "Diederick C. Niehorster" <dcnieho@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] FFmpeg 5.0.1
Date: Tue, 29 Mar 2022 23:12:47 +0200
Message-ID: <CABcAi1hSOs8uX00dFNfTacVV-+dsY+EBdVWyLm1=-0rNrNM1aw@mail.gmail.com> (raw)
In-Reply-To: <20220329210822.GM2829255@pb2>
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".
next prev parent reply other threads:[~2022-03-29 21:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 23:31 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 [this message]
2022-03-29 21:21 ` Michael Niedermayer
2022-03-29 15:23 ` Oneric
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='CABcAi1hSOs8uX00dFNfTacVV-+dsY+EBdVWyLm1=-0rNrNM1aw@mail.gmail.com' \
--to=dcnieho@gmail.com \
--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