From: Bernd Petrovitsch <bernd@petrovitsch.priv.at>
To: Joe Perches <joe@perches.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org, Christoph Hellwig <hch@lst.de>
Subject: Re: get_maintainers.pl is rude, was Re: [PATCH 05/19] USB: inode.c: move assignment out of if () block
Date: Sat, 02 May 2015 13:16:14 +0200 [thread overview]
Message-ID: <1430565386.20751.6.camel@thorin> (raw)
In-Reply-To: <20150430125403.GA22948@lst.de>
On Don, 2015-04-30 at 14:54 +0200, Christoph Hellwig wrote:
> 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.
[...]
Does it make sense(Is it enough to filter the changes to only include
changes from the last 6 months or so (if there are newer changes;-)?
People probably don't care if they didn't touch it for ages anyway.
Or ignore changes which touch only a few lines completely (to not
include typo fixes or trivial fixups)?
Kind regards,
Bernd
--
"I dislike type abstraction if it has no real reason. And saving
on typing is not a good reason - if your typing speed is the main
issue when you're coding, you're doing something seriously wrong."
- Linus Torvalds
next prev parent reply other threads:[~2015-05-02 11:16 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 [this message]
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=1430565386.20751.6.camel@thorin \
--to=bernd@petrovitsch.priv.at \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--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