git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Olaf Hering <olaf@aepfle.de>
Cc: Jeff King <peff@peff.net>,
	linux-kernel@vger.kernel.org, git@vger.kernel.org
Subject: Re: get_maintainer.pl sends bogus addresses to git send-email
Date: Tue, 07 Apr 2020 10:39:58 -0700	[thread overview]
Message-ID: <5d05fca7bcdeb57ed31fbbfc66d4cf7224e56f92.camel@perches.com> (raw)
In-Reply-To: <20200407192949.586159e7.olaf@aepfle.de>

On Tue, 2020-04-07 at 19:29 +0200, Olaf Hering wrote:
> Am Tue, 07 Apr 2020 10:18:41 -0700
> schrieb Joe Perches <joe@perches.com>:
> 
> > You need to add --norolestats on the get_maintainer command line
> 
> Thanks, this can be used as a workaround for the time being.
> Not sure why anyone would actually care about such details in default mode...

Because the default is
"tell me more about the maintainers of a particular file".
which can include not just the default maintainers of
a particular file within a subsystem, but the also info
about the people that actually apply patches to files.

For instance, a patch made to a file often has a nominal
maintainer that doesn't actually apply the patches but
that maintainer may review or approve but not actually
be the upstream path for acceptance of the patch.




  reply	other threads:[~2020-04-07 17:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-07 15:40 get_maintainer.pl sends bogus addresses to git send-email Olaf Hering
2020-04-07 17:02 ` Jeff King
2020-04-07 17:18   ` Joe Perches
2020-04-07 17:29     ` Olaf Hering
2020-04-07 17:39       ` Joe Perches [this message]
2020-04-07 17:44     ` Jeff King
2020-04-07 21:56       ` Joe Perches
2020-04-08 17:28         ` Jeff King

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=5d05fca7bcdeb57ed31fbbfc66d4cf7224e56f92.camel@perches.com \
    --to=joe@perches.com \
    --cc=git@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olaf@aepfle.de \
    --cc=peff@peff.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).