Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH 2/2] doc/developer: Code pushed without patches on ffmpeg-devel must be announced on the ML
Date: Thu, 24 Aug 2023 22:23:47 +0200
Message-ID: <AS8P250MB0744103B5A605A267DF2BBC68F1DA@AS8P250MB0744.EURP250.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <25cb7b68-493e-52dd-179a-58d817734906@gmail.com>

James Almer:
> On 8/24/2023 4:56 PM, Michael Niedermayer wrote:
>> Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
>> ---
>>   doc/developer.texi | 9 +++++++++
>>   1 file changed, 9 insertions(+)
>>
>> diff --git a/doc/developer.texi b/doc/developer.texi
>> index 383120daaa..1c0091fc74 100644
>> --- a/doc/developer.texi
>> +++ b/doc/developer.texi
>> @@ -856,6 +856,15 @@ way to get everyone's patches reviewed sooner.
>>   Reviews must be constructive and when rejecting a patch the reviewer
>> must explain
>>   their reasons and ideally suggest an alternative approach.
>>   +If a change is pushed without being sent to ffmpeg-devel, the
>> developer
>> +pushing it must annouce doing so on the ffmpeg-devel mailing list
>> immedeatly.
> 
> immediately.
> 
> This chunk is ok, but...
> 
>> +@example
>> +forgot a semicolon in this patch, pushed a seperate fix
>> +pushed my new autograd engine and stable diffusion filter. Didnt want to
>> +go through the bikeshed if that belongs in FFmpeg, go to the GA if
>> you want
>> +it removed. Otherwise Just tell me what i should improve and ill look
>> into it.
>> +@end example
> 
> ...this one isn't. It's very passive aggressive and not informative at all.
> This instead should state that patches pushed without passing through
> the ML have to either be trivial, to push fixes to mistakes in recently
> pushed changes that did go through the ML, or for code you maintain.
> 

The maintainer exception has actually been removed in
6a3e174ad1921ba6aec473a2224c71610de3329b.

- Andreas

_______________________________________________
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".

      reply	other threads:[~2023-08-24 20:22 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-24 19:56 [FFmpeg-devel] [PATCH 0/2] [RFC] doc/developer patch review improvements Michael Niedermayer
2023-08-24 19:56 ` [FFmpeg-devel] [PATCH 1/2] doc/developer: Reviews must be constructive Michael Niedermayer
2023-08-25  1:56   ` Vittorio Giovara
2023-08-25  6:46     ` Nicolas George
2023-08-25  9:22       ` Paul B Mahol
2023-08-25 17:23       ` Vittorio Giovara
2023-08-25 14:06     ` Anton Khirnov
2023-08-25 14:22   ` Rémi Denis-Courmont
2023-08-25 14:58     ` Anton Khirnov
2023-08-25 15:09       ` Rémi Denis-Courmont
2023-08-25 15:23         ` Anton Khirnov
2023-08-25 17:26           ` Vittorio Giovara
2023-08-25 17:35             ` Anton Khirnov
2023-08-25 17:34         ` Leo Izen
2023-08-25 17:39           ` Nicolas George
2023-08-24 19:56 ` [FFmpeg-devel] [PATCH 2/2] doc/developer: Code pushed without patches on ffmpeg-devel must be announced on the ML Michael Niedermayer
2023-08-24 20:04   ` Andreas Rheinhardt
2023-08-25 15:34     ` Michael Niedermayer
2023-08-25 15:36       ` Jean-Baptiste Kempf
2023-08-25 15:47         ` Paul B Mahol
2023-08-25 16:27         ` Nicolas George
2023-08-25 16:33           ` Jean-Baptiste Kempf
2023-08-25 17:16             ` Nicolas George
2023-08-25 17:25               ` James Almer
2023-08-25 17:42                 ` Nicolas George
2023-08-25 21:41                   ` Ronald S. Bultje
2023-08-24 20:06   ` James Almer
2023-08-24 20:23     ` Andreas Rheinhardt [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=AS8P250MB0744103B5A605A267DF2BBC68F1DA@AS8P250MB0744.EURP250.PROD.OUTLOOK.COM \
    --to=andreas.rheinhardt@outlook.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