From: "Rémi Denis-Courmont" <remi@remlab.net> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org> Subject: Re: [FFmpeg-devel] Forgejo entry threshold Date: Fri, 08 Aug 2025 10:14:52 +0700 Message-ID: <29D4DB17-876E-4077-922D-3F4B4771A2E0@remlab.net> (raw) In-Reply-To: <aJSeDI2zAhr2LfI2@phare.normalesup.org> Le 7 août 2025 19:37:32 GMT+07:00, Nicolas George <george@nsup.org> a écrit : >Rémi Denis-Courmont (HE12025-08-07): >> Sure. You can send a list of patch files... And make it even more difficult to review, > >What? An attached file is not more difficult to review than a mail sent >directly by git, If your mail client treats attachments the same as inline text, your mail client is very badly broken as a mail client. And if not, then it is obviously much more cumbersome to review an attachment. Also replying to multiple patches in a single mail makes everyone else's life miserable for tracking the review. But more importantly, email has all the fundamental problems that I already raised several times in previous threads. It simply can't compete with something that's designed for code review and actually tracks and organises relevant metadata. > and both are more convenient than a web monstrosity? Unless you're using an extremely old or underpowered system that can't run a reasonably recent web browser, no. And if you do, then good luck compiling FFmpeg with it. >Guys, have you never spend five minutes learning how to use mail? Yeah, we gave. And that definitely doesn't cover sending and reviewing patches because that's not what email was intended for. Git didn't even exist then. _______________________________________________ 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-08-08 3:15 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <20250804143901.82ED768C3C2@ffbox0-bg.ffmpeg.org> 2025-08-04 14:45 ` Nicolas George 2025-08-04 14:47 ` Hendrik Leppkes 2025-08-04 14:49 ` Nicolas George 2025-08-04 15:06 ` Leon Grutters 2025-08-05 13:10 ` Nicolas George 2025-08-05 14:17 ` Kacper Michajlow 2025-08-07 10:42 ` Nicolas George 2025-08-06 5:52 ` Rémi Denis-Courmont 2025-08-06 8:11 ` Nicolas George 2025-08-07 12:30 ` Rémi Denis-Courmont 2025-08-07 12:37 ` Nicolas George 2025-08-08 3:14 ` Rémi Denis-Courmont [this message] 2025-08-09 18:39 ` Nicolas George 2025-08-05 13:07 ` Nicolas George
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=29D4DB17-876E-4077-922D-3F4B4771A2E0@remlab.net \ --to=remi@remlab.net \ --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