Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Leon Grutters <gruttersleonbot2@gmail.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] Forgejo entry threshold
Date: Mon, 4 Aug 2025 17:06:07 +0200
Message-ID: <9321627b-8594-4483-923b-cfaef4f09c6c@gmail.com> (raw)
In-Reply-To: <aJDHirFSrzfJXqzx@phare.normalesup.org>

On 8/4/25 4:45 PM, Nicolas George wrote:
> Dummy_test_user (HE12025-08-04):
>> PR #20112 opened by Dummy_test_user
>> URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20112
>> Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20112.patch
>>
>> I did that pull request to see what is preventing me from submitting crappy code.
>> Apparently nothing.
> Hi.
>
> That was me. Thank you for ensuring it went to the mailing-list.
>
> But…
>
> I could register an account and create a pull request without ever
> reading the coding-style rules in doc/developer.texi, and the pull
> requests has red patcheck:
>
> mismatching doxy params
> + * @param erbut  useless
> + * @param ernut  does nothing
>
> That is not good.
>
> If nothing better comes to mind to exclude crappy code, could we at
> least condition creating an account to answering a 10 questions quiz
> about our coding conventions?
>
> Regards,
>
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.

_______________________________________________
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".

      parent reply	other threads:[~2025-08-04 15:06 UTC|newest]

Thread overview: 4+ 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 [this message]

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=9321627b-8594-4483-923b-cfaef4f09c6c@gmail.com \
    --to=gruttersleonbot2@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