From: Nicolas George <george@nsup.org> 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 16:09:19 +0100 Message-ID: <Z8HRn6hFGIYO21OY@phare.normalesup.org> (raw) In-Reply-To: <aafb10e5-fd1e-417a-bfd8-2130dbd4b7e9@mur.at> martin schitter (HE12025-02-28): > This kind of checks should better happen in some kind of CI based pipeline > supporting direct feedback to the contributors before accepting the patches > for any further human review by maintainers or on public mailing lists. > > That's why I really like GitLab and similar tools. Developing in 2025: the project uses a monolithic tool, everything is in this tool, everybody has to use it, whether they like it or not. Developing in the early 2000s when FFmpeg grew: low-level tools are provided, every developer is free to integrate them in their favored working process, and indeed expected to do so. Developers from 2025 when confronted with a project from the early 2000s: “What's a script? Help!! What's a keyboard?” [insert here a picture of a hen who found a knife] > As long as languages do not simply enforce only one preferred coding style > (like for example in rust and deno) you'll never find a solution, which > makes everyone happy. Hard rules on cosmetic matters are a terrible idea, whether they are enforced at the level of the language or downstream from it. Regards, -- Nicolas George _______________________________________________ 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 15:09 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 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 [this message] 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=Z8HRn6hFGIYO21OY@phare.normalesup.org \ --to=george@nsup.org \ --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