From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] 5.0 release
Date: Wed, 15 Dec 2021 16:15:35 +0100
Message-ID: <20211215151535.GV2829255@pb2> (raw)
In-Reply-To: <CABcAi1itQOE8kjuvmnvYoU+7VsN-TtNXxRaZtno+XwpJgmzFLg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1852 bytes --]
On Wed, Dec 15, 2021 at 04:08:43PM +0100, Diederick C. Niehorster wrote:
> Hi Michael,
>
> On Wed, Dec 15, 2021 at 3:52 PM Michael Niedermayer
> <michael@niedermayer.cc> wrote:
> >
> > On Tue, Dec 14, 2021 at 05:42:01PM +0100, Diederick C. Niehorster wrote:
> > > Hi Michael,
> > >
> > > On Tue, Dec 14, 2021 at 5:19 PM Michael Niedermayer
> > > <michael@niedermayer.cc> wrote:
> > > >
> > > >
> > > > The patches do not say in their commit messages that they have been reviewed
> > > > maybe you want to repost them with that changed.
> > >
> > > Thanks for having a look!
> > > I have mentioned this here:
> > > https://ffmpeg.org/pipermail/ffmpeg-devel/2021-December/289461.html
> > >
> > > Or do you mean that for each specific patch, if there were previous
> > > review comments, i should mention that it was updated in response to
> > > the review? For some that may be hard (e.g. i was asked to change the
> > > order of some commits).
> >
> > Patches which where approved already and not changed since then could
> > contain that information in the commit message. We tend to use some
> > Reviewed-by: ...
> > for that
> > that may speed up future review and commit
> >
> > I dont know dshow and dont have a proper setup to test it so i wont be
> > applying or reviewing these patches
>
> Ah, i see. I have made changes here in response to other review
> comment since i got that LGTM for the series. I'll contact the dshow
> maintainer again for that (I assume he would be the only one who
> should be committing my patchset?).
anyone with commit rights could apply after a review by someone who knows
the code. Of course could != will
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Avoid a single point of failure, be that a person or equipment.
[-- 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".
next prev parent reply other threads:[~2021-12-15 15:15 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20211125171932.GC2829255@pb2>
[not found] ` <20211213152557.GL2829255@pb2>
[not found] ` <CABcAi1jFnkGd-dyLy_iOHhKEVUz=OPYXp23X326_6okM+zW8Aw@mail.gmail.com>
[not found] ` <20211214161924.GM2829255@pb2>
[not found] ` <CABcAi1h45bkw4rmYJYEJrEaqOybbFvqXZFAAJ6F5=Mo4+BPHVg@mail.gmail.com>
2021-12-15 14:52 ` Michael Niedermayer
2021-12-15 15:08 ` Diederick C. Niehorster
2021-12-15 15:15 ` Michael Niedermayer [this message]
[not found] ` <3238136b-1f43-49ae-b2d6-ce98b98e24f0@www.fastmail.com>
2021-12-22 14:03 ` Michael Niedermayer
2021-12-22 14:05 ` James Almer
2021-12-22 16:44 ` Jean-Baptiste Kempf
2021-12-27 23:55 ` Michael Niedermayer
2021-12-31 16:52 ` Michael Niedermayer
2021-12-31 17:15 ` Gyan Doshi
2021-12-31 19:40 ` Michael Niedermayer
2022-01-02 14:12 ` Anton Khirnov
2022-01-02 14:29 ` James Almer
2022-01-02 14:50 ` Zane van Iperen
2022-01-02 15:09 ` James Almer
2022-01-02 15:52 ` Zane van Iperen
2022-01-02 16:28 ` Lynne
2022-01-02 17:11 ` Michael Niedermayer
2022-01-02 18:12 ` Lynne
2022-01-02 22:29 ` Michael Niedermayer
2022-01-02 22:32 ` Michael Niedermayer
2022-01-03 5:31 ` Jean-Baptiste Kempf
2022-01-03 16:14 ` Michael Niedermayer
2022-01-03 17:17 ` Hendrik Leppkes
2022-01-03 17:19 ` Hendrik Leppkes
2022-01-03 18:04 ` Paul B Mahol
2022-01-03 18:58 ` Michael Niedermayer
2022-01-03 19:25 ` Paul B Mahol
2022-01-03 20:14 ` Michael Niedermayer
2022-01-03 20:29 ` Paul B Mahol
2022-01-03 20:36 ` Michael Niedermayer
2022-01-03 19:23 ` Michael Niedermayer
2022-01-04 2:11 ` Soft Works
2021-12-31 19:08 ` Lynne
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=20211215151535.GV2829255@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