linux-kernel - Re: get_maintainers.pl is rude, was Re: [PATCH 05/19] USB: inode.c: move assignment out of if () block

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 02 May 2015 13:16:14 +0200
From:	Bernd Petrovitsch <bernd@...rovitsch.priv.at>
To:	Joe Perches <joe@...ches.com>
Cc:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	linux-kernel@...r.kernel.org, Christoph Hellwig <hch@....de>
Subject: Re: get_maintainers.pl is rude, was Re: [PATCH 05/19] USB: inode.c:
 move assignment out of if () block

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/