Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "J, Dekker" <jdek@itanimul.li>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] tools: add general_assembly.pl
Date: Wed, 16 Feb 2022 02:46:53 +0100
Message-ID: <1ddf9075-f138-438b-8fc2-3c27d648f12f@itanimul.li> (raw)
In-Reply-To: <4c488008-c561-4399-8a45-231b1eb8a2e3@beta.fastmail.com>

On 15/02/2022 17:46, Jean-Baptiste Kempf wrote:
> Hello,
> 
> On Tue, 15 Feb 2022, at 12:50, J. Dekker wrote:
>>   This was rejected last time but I would really like to get this in the
>>   tools or at least publicly recorded on mailing list since the script
>>   was updated.
> 
> Why was this rejected?

It was blocked by Nicolas as the procedure to determine the general 
assembly was not fully decided.

>> +        foreach my $commit (@commits) {
>> +            if ($commit =~ /\n[\w\/]+\.(c|h|S|asm)/) {
>> +                $true++;
>> +            }
> 
> Why do we filter on those file types? .md, .pl and other things for docs are active in the community.

It was just discussed at the in person meeting, our documentation states 
otherwise and I think we should stick to the documentation here. It 
doesn't make that much sense to filter out people who have majority 
documentation commits either--20 documentation commits is still a 
significant enough contribution.

See updated patch.

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

      reply	other threads:[~2022-02-16  1:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-15 11:50 J. Dekker
2022-02-15 16:46 ` Jean-Baptiste Kempf
2022-02-16  1:46   ` J, Dekker [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=1ddf9075-f138-438b-8fc2-3c27d648f12f@itanimul.li \
    --to=jdek@itanimul.li \
    --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