All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2 4/4] get_maintainer.pl: restrict cases where it falls back to --git
Date: Wed, 22 Oct 2014 15:45:32 +0200	[thread overview]
Message-ID: <5447B4FC.2010909@redhat.com> (raw)
In-Reply-To: <8761fcclf8.fsf@blackfin.pond.sub.org>



On 10/22/2014 02:56 PM, Markus Armbruster wrote:
> Paolo Bonzini <pbonzini@redhat.com> writes:
> 
>> The list emitted by --git-fallback often leads inexperienced contributors
>> to add pointless CCs.  While not discouraging usage of --git-fallback,
>> we want to:
>>
>> 1) disable the fallback if only some files lack a maintainer
>>
>>     $ scripts/get_maintainer.pl -f util/cutils.c hw/ide/core.c
>>     Kevin Wolf <kwolf@redhat.com> (odd fixer:IDE)
>>     Stefan Hajnoczi <stefanha@redhat.com> (odd fixer:IDE)
>>
>> This behavior is taken even if --git-fallback is specified.
>>
>> 2) warn the contributors about what we're doing, asking them to use their
>> common sense:
>>
>>     $ scripts/get_maintainer.pl -f util/cutils.c
>>     get_maintainer.pl: No maintainers found, printing recent contributors.
>>     get_maintainer.pl: Do not blindly cc: them on patches!  Use common sense.
>>
>>     Luiz Capitulino <lcapitulino@redhat.com> (commit_signer:1/2=50%)
>>     ...
>>     $
>>
>> Explicitly disabling the fallback will not result in the warning message:
>>
>>     $ scripts/get_maintainer.pl -f util/cutils.c   --no-git-fallback
>>     $ echo $?
>>     1
>>
>> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
>> ---
>>  scripts/get_maintainer.pl | 9 +++++++++
>>  1 file changed, 9 insertions(+)
>>
>> diff --git a/scripts/get_maintainer.pl b/scripts/get_maintainer.pl
>> index 7c6d186..f4fee27 100755
>> --- a/scripts/get_maintainer.pl
>> +++ b/scripts/get_maintainer.pl
>> @@ -633,6 +633,15 @@ sub get_maintainers {
>>      }
>>  
>>      if ($email) {
>> +	if (! $interactive) {
>> +	    $email_git_fallback = 0 if @email_to > 0 || @list_to > 0 || $email_git || $email_git_blame;
>> +	    if ($email_git_fallback) {
>> +	        print STDERR "get_maintainer.pl: No maintainers found, printing recent contributors.\n";
>> +	        print STDERR "get_maintainer.pl: Do not blindly cc: them on patches!  Use common sense.\n";
>> +	        print STDERR "\n";
>> +            }
>> +        }
>> +
>>  	foreach my $file (@files) {
>>  	    if ($email_git || ($email_git_fallback &&
>>  			       !$exact_pattern_match_hash{$file})) {
> 
> I liked v1 better.

Me too, but we can start with this.  It's better than the status quo,
and the difference overall is small (the important part is disabling
fallback---with no message---on @email_to || @list_to).

Paolo

      reply	other threads:[~2014-10-22 13:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-22 10:41 [Qemu-devel] [PATCH v2 4/4] get_maintainer.pl: restrict cases where it falls back to --git Paolo Bonzini
2014-10-22 12:56 ` Markus Armbruster
2014-10-22 13:45   ` Paolo Bonzini [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=5447B4FC.2010909@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=armbru@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.