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: Wed, 06 Aug 2025 12:52:21 +0700
Message-ID: <B5D366C2-83E1-4171-A9E8-594BB45B2CAA@remlab.net> (raw)
In-Reply-To: <9321627b-8594-4483-923b-cfaef4f09c6c@gmail.com>
Le 4 août 2025 22:06:07 GMT+07:00, Leon Grutters <gruttersleonbot2@gmail.com> a écrit :
>Is it that much harder to submit a patch on the ML? All you do is sign up for the ML, run one git command and then attach it to an email and click send.
I don't know how much is that much. It is harder, at least the *first* time, though not hard enough to deter a "vibe coder". But it is exclusionary, as not everyone can get a working reputable outbound SMTP server.
That said, I prefer a forge to facilitate the review process, not the submission process. Judging by earlier discussions, I am far from the only one.
_______________________________________________
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-06 5:52 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 [this message]
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
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=B5D366C2-83E1-4171-A9E8-594BB45B2CAA@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