From: Joe Perches <joe@perches.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: get_maintainers.pl is rude, was Re: [PATCH 05/19] USB: inode.c: move assignment out of if () block
Date: Tue, 05 May 2015 09:32:27 -0700 [thread overview]
Message-ID: <1430843547.7191.28.camel@perches.com> (raw)
In-Reply-To: <20150505153832.GA4885@lst.de>
On Tue, 2015-05-05 at 17:38 +0200, Christoph Hellwig wrote:
> On Sat, May 02, 2015 at 06:52:19AM -0700, Joe Perches wrote:
> > > I can see the point to guess it by
> > > non-maintainer signoffs, but authorship is plain wrong and highly
> > > annoying.
The commit signer/author lookup is only done for files
that do not have a specified maintainer.
> > That's an assertion, but you've neglected to give
> > a rationale for it. I think authorship is quite a
> > good reason to be cc'd on something as given that
> > you've spent the effort to originate code, you're
> > also quite likely to be interested in patches for
> > that code.
>
> It's not. Patch authorship != driver authorship. There are people
> like me or Al that keep fixing interface all over the tree. That doesn't
> really mean I need patches touching those same files again in my inbox.
> I generally couldn't care less, and if I do I will pick it up through
> the mailinglists.
There are also people that author patches that are
interested in follow-on changes too.
I also touch many files across the kernel, and I get
the odd random patches I'm not uninterested in. I have
no issue with the 3 seconds it takes to ignore them.
> If we can't get the bullshit heuristics fixed properly please add this
> support, and feel free to use me as the initial seed for it.
As I said, I'm not interested in doing anything to any
.ignore file.
I'll submit the patch to the script, you can submit the
patch to add your name to the .ignore file.
cheers, Joe
prev parent reply other threads:[~2015-05-05 16:32 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 ` get_maintainers.pl is rude, was Re: [PATCH 05/19] USB: inode.c: move assignment out of if () block Christoph Hellwig
2015-05-02 11:16 ` Bernd Petrovitsch
2015-05-02 13:52 ` Joe Perches
2015-05-05 15:38 ` Christoph Hellwig
2015-05-05 16:32 ` Joe Perches [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=1430843547.7191.28.camel@perches.com \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--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