Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Lynne <dev@lynne.ee>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] bsf: use standard include paths
Date: Wed, 10 Apr 2024 15:47:50 +0200 (CEST)
Message-ID: <Nv7Cuo7--3-9@lynne.ee> (raw)
In-Reply-To: <171272487341.22242.12636501135933839434@lain.khirnov.net>

Apr 10, 2024, 06:54 by anton@khirnov.net:

> Quoting James Almer (2024-04-10 03:23:46)
>
>> On 4/9/2024 10:11 PM, Andrew Kelley wrote:
>> > On 4/9/24 17:04, Lynne wrote:
>> >> LGTM.
>> >> That's how I wrote the AAC patchset as well.
>> >
>> > Thank you for the review, Lynne.
>> >
>> > What is the next step? I do not have commit access.
>>
>> Applied it, thanks.
>>
>
> WTF?
>
> Please revert immediately.
>

In the past, even for sketchy commits with many follow-up fixes needed,
and with multiple reverts requested, no one dared to revert someone
else's commits out of fear of starting a revert war.

You didn't issue a warning that you were going to revert, you didn't
ask any of us who approved it, and you hardly allowed for anyone
involved to respond. The only reason given on IRC was:
> <psykose> rather than argue about whatever this is it would be more interesting to know what in the patch is controversial
> <@elenril> I don't like it

Please don't do this again. This project isn't a dictatorship, and it
creates precedence for someone to do the same with your commits.

What don't you like about this commit? It eliminates ambiguity
and any danger of header conflicts for subsystems being switched
to local folders.
_______________________________________________
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:[~2024-04-10 13:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-09 21:13 Andrew Kelley
2024-04-10  0:04 ` Lynne
2024-04-10  1:11   ` Andrew Kelley
2024-04-10  1:23     ` James Almer
2024-04-10  4:54       ` Anton Khirnov
2024-04-10 13:47         ` Lynne [this message]
2024-04-10 14:11 ` Andreas Rheinhardt
2024-04-10 18:35   ` Paul B Mahol
2024-04-10 21:06   ` Andrew Kelley
2024-04-10 21:27     ` Andreas Rheinhardt

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=Nv7Cuo7--3-9@lynne.ee \
    --to=dev@lynne.ee \
    --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