From: Gyan Doshi <ffmpeg@gyani.pro>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [FFmpeg-cvslog] doc/filters: clarify behaviour of weights in amix
Date: Tue, 9 Aug 2022 17:14:08 +0530
Message-ID: <c6bb7d4d-2f29-67bb-b726-967c001b803b@gyani.pro> (raw)
In-Reply-To: <CA+anqdyk-AL7kB2+5LfZahRXXj93HzLkMWwmO=BxVOfsNZT0tw@mail.gmail.com>
On 2022-08-09 04:55 pm, Hendrik Leppkes wrote:
> On Tue, Aug 9, 2022 at 12:46 PM Gyan Doshi <ffmpeg@gyani.pro> wrote:
>>
>>
>> On 2022-08-09 04:00 pm, Ronald S. Bultje wrote:
>>> On Tue, Aug 9, 2022 at 5:36 PM Gyan Doshi <ffmpeg@gyani.pro> wrote:
>>>
>>>> On 2022-08-09 02:57 pm, Anton Khirnov wrote:
>>>>> Quoting Gyan Doshi (2022-08-09 11:22:39)
>>>>>> I am a docs maintainer so I push these directly.
>>>>> All patches should go through the mailing list, so other people get the
>>>>> opportunity to comment on them.
>>>> I do that for more extensive changes.
>>>>
>>>> As the guidelines say,
>>>>
>>>> "Send your changes as patches to the ffmpeg-devel mailing list
>>> and
>>>
>>>
>>> if
>>>> the code maintainers say OK, you may commit. This does not apply to
>>>> files you wrote and/or maintain."
>>> That should make the intent of the sentence quoted clear.
>> 'This' refers to the entire preceding sentence. If it was otherwise, it
>> would be incompatible with the 2nd way mentioned at
>> http://www.ffmpeg.org/developer.html#Contributing
>>
>> I'm not wedded to the policy as stated in the current docs, but the
>> current docs are clear that maintainers can push directly.
>>
> If several people disagree on the interpretation, its clearly not as
> "clear" as you claim it to be.
Yes, but only one person (Ronald) disagreed. Anton said it was outdated.
But your objection is weird considering that Ronald affirmed that the
intent was clear. That intent just happens to be opposite to what I
think it is.
This continued discussion is pointless. All this needs is a patch for
what the new unambiguous policy should be.
Regards,
Gyan
_______________________________________________
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".
prev parent reply other threads:[~2022-08-09 11:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220809083015.68AB5411A20@natalya.videolan.org>
2022-08-09 9:14 ` Anton Khirnov
[not found] ` <ecd451da-b0c2-da69-4e0a-7a87647c37a4@gyani.pro>
2022-08-09 9:27 ` Anton Khirnov
2022-08-09 9:36 ` Gyan Doshi
2022-08-09 9:45 ` Anton Khirnov
2022-08-09 9:48 ` Gyan Doshi
2022-08-09 10:30 ` Ronald S. Bultje
2022-08-09 10:45 ` Gyan Doshi
2022-08-09 11:25 ` Hendrik Leppkes
2022-08-09 11:44 ` Gyan Doshi [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=c6bb7d4d-2f29-67bb-b726-967c001b803b@gyani.pro \
--to=ffmpeg@gyani.pro \
--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