From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] doc/developer: Better {} style rule
Date: Fri, 28 Feb 2025 01:58:59 +0100
Message-ID: <20250228005859.GM4991@pb2> (raw)
In-Reply-To: <CAHGibzEtxPuUkbpaLbVv0dd2CYZi2bMvtR4CJB_uS=5bVA7+CA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1626 bytes --]
On Thu, Feb 27, 2025 at 07:40:14PM -0500, Devin Heitmueller wrote:
> On Thu, Feb 27, 2025 at 5:57 PM James Almer <jamrial@gmail.com> wrote:
> > > 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.
>
> In my opinion, developers generally want to clean up style issues
> prior to submission. The problem with doing it in a CI job is that it
> will just tell you after the fact that your patch didn't meet the
> coding standards and you have to revise and resubmit. The alternative
> is for the CI job to "fix" the patch to conform, which people
> generally don't want because what they submitted is different than
> what gets committed.
>
> For what it's worth, with the Linux Kernel we solved this years ago
> with a "checkpatch.pl" which developers can run prior to committing.
> Thus I could quickly run checkpatch.pl, fix anything it complains
> about, and then run git commit and be confident that it conforms to
> the standard. Personally I prefer this approach as it lets me fix the
> patches prior to submission, and the CI system isn't changing things
> without my knowledge.
we have tools/patcheck :)
I have the feeling we started forgeting about it
And I also think changing submissions in CI is problematic.
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
He who knows, does not speak. He who speaks, does not know. -- Lao Tsu
[-- 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:[~2025-02-28 0:59 UTC|newest]
Thread overview: 22+ 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
2025-02-28 0:40 ` Devin Heitmueller
2025-02-28 0:58 ` Michael Niedermayer [this message]
2025-02-28 7:53 ` Nicolas George
2025-02-28 10:13 ` Marvin S.
2025-02-28 14:07 ` Devin Heitmueller
2025-02-28 14:16 ` Nicolas George
2025-02-28 14:21 ` martin schitter
2025-02-28 15:09 ` Nicolas George
2025-02-28 15:13 ` Vittorio Giovara
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
2025-02-28 13:44 ` Vittorio Giovara
2025-02-28 15:12 ` Michael Niedermayer
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=20250228005859.GM4991@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