public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Joe Perches <joe@perches.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org
Subject: get_maintainers.pl is rude, was Re: [PATCH 05/19] USB: inode.c: move assignment out of if () block
Date: Thu, 30 Apr 2015 14:54:03 +0200	[thread overview]
Message-ID: <20150430125403.GA22948@lst.de> (raw)
In-Reply-To: <20150430124004.GA17070@kroah.com>

On Thu, Apr 30, 2015 at 02:40:04PM +0200, Greg Kroah-Hartman wrote:
> scripts/get_maintainer.pl is bringing up your name for this file as you
> have modified it in the past:

I've probably modified a large part of files in the kernel in the past.

And I'm annoyed about this stupid behavior in get_maintainers.pl.

Joe, can you please fix your bloody script to not report me for every
goddamnt file I touched once?  Authorship of changes to a file is
a completely wrong metric.  I can see the point to guess it by
non-maintainer signoffs, but authorship is plain wrong and highly
annoying.

If you're unwilling to fix this please at least add a get_maintainers.ignore
file and add me as the first entry.  Thanks!

       reply	other threads:[~2015-04-30 12:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1430386388-15462-1-git-send-email-gregkh@linuxfoundation.org>
     [not found] ` <1430386388-15462-5-git-send-email-gregkh@linuxfoundation.org>
     [not found]   ` <20150430093608.GA18432@lst.de>
     [not found]     ` <20150430124004.GA17070@kroah.com>
2015-04-30 12:54       ` Christoph Hellwig [this message]
2015-05-02 11:16         ` get_maintainers.pl is rude, was Re: [PATCH 05/19] USB: inode.c: move assignment out of if () block Bernd Petrovitsch
2015-05-02 13:52         ` Joe Perches
2015-05-05 15:38           ` Christoph Hellwig
2015-05-05 16:32             ` Joe Perches

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=20150430125403.GA22948@lst.de \
    --to=hch@lst.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox