From: James Almer <jamrial@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] doc/developer: Better {} style rule
Date: Thu, 27 Feb 2025 19:57:14 -0300
Message-ID: <96fd7a0f-d755-4726-931c-c317a5f6d541@gmail.com> (raw)
In-Reply-To: <CABLWnS8dpuCcAidg07FZROPgUSUMLL+oF8n+V=oO2tb1pDpVPA@mail.gmail.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1326 bytes --]
On 2/27/2025 7:53 PM, Vittorio Giovara wrote:
> On Thu, Feb 27, 2025 at 11:47 PM <epirat07@gmail.com> wrote:
>
>> On 27 Feb 2025, at 2:10, Michael Niedermayer wrote:
>>
>>> Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
>>> ---
>>> doc/developer.texi | 11 +++++------
>>> 1 file changed, 5 insertions(+), 6 deletions(-)
>>>
>>> diff --git a/doc/developer.texi b/doc/developer.texi
>>> index a1bfe180c9b..6a753f99da6 100644
>>> --- a/doc/developer.texi
>>> +++ b/doc/developer.texi
>>> @@ -179,18 +179,17 @@ int fields = ilace ? 2 : 1;
>>> @end example
>>>
>>> @item
>>> -No braces around single-line blocks:
>>> +No braces around single-line blocks, unless they are followed by an
>> else (to keep future patches cleaner)
>>>
>>
>> I agree with this, however people in the past pointed it out when new code
>> did this, IIRC.
>>
>> So if we merge this, people should stop flagging this in reviews, else its
>> frustrating
>> for new contributors following the documentation and then getting
>> contradicting reviews.
>
>
> would loooove a format defining script with a prehook that formats your
> patches before sending <3
That can be done automatically as one of the many jobs CI runs once we
move to forgejo/gitlab. Same with every other check in patcheck.
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 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:[~2025-02-27 22:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 1:10 Michael Niedermayer
2025-02-27 22:46 ` epirat07
2025-02-27 22:53 ` Vittorio Giovara
2025-02-27 22:57 ` James Almer [this message]
2025-02-28 0:40 ` Devin Heitmueller
2025-02-28 0:58 ` Michael Niedermayer
2025-02-28 7:53 ` Nicolas George
2025-02-28 10:13 ` Marvin S.
2025-02-28 1:11 ` Soft Works
2025-02-27 23:14 ` Michael Niedermayer
2025-02-27 23:25 ` epirat07
2025-02-28 3:22 ` Michael Niedermayer
2025-02-28 2:25 ` Lynne
2025-02-28 2:33 ` Michael Niedermayer
2025-02-28 12:24 ` 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=96fd7a0f-d755-4726-931c-c317a5f6d541@gmail.com \
--to=jamrial@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