linux-kernel - Re: RFC: get_maintainer.pl: append reason for cc to the name by default

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] [day] [month] [year] [list]

Message-ID: <20100928043704.GA7455@sirena.org.uk>
Date:	Tue, 28 Sep 2010 05:37:05 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Joe Perches <joe@...ches.com>
Cc:	Ted Ts'o <tytso@....edu>, Florian Mickler <florian@...kler.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Stephen Hemminger <shemminger@...tta.com>,
	Wolfram Sang <w.sang@...gutronix.de>,
	linux-kernel@...r.kernel.org
Subject: Re: RFC: get_maintainer.pl: append reason for cc to the name by
	default

On Mon, Sep 27, 2010 at 02:16:45PM -0700, Joe Perches wrote:
> On Mon, 2010-09-27 at 16:47 -0400, Ted Ts'o wrote:

> Mark Brown said: http://lkml.org/lkml/2010/9/10/116
> ----------------------------------------------------
> On Fri, Sep 10, 2010 at 03:04:26AM -0700, Joe Perches wrote:

> > It'd be great if the ARM/embedded folk would spend
> > some effort improving the MAINTAINERS file pattern
> > coverage.

> Half the problem is that a lot of drivers aren't maintained by the
> people who wrote them - for example, they wrote the driver to get a
> board working but have no ongoing interest or can only really comment on
> the one specific configuration used on their particular hardware.  This
> means getting people to add MAINTAINERS entries is a bit more tricky
> than it needs to be, even if they could offer useful review on changes.
> ---------------------------------------------------

> So for Mark's case, the current behavior works reasonably well.

Actually I've got pretty much all the problems Ted has with it - when I
use get_maintainer it's done in conjunction with my knowledge of who the
people who turn up are and what the chances are that they'd have been
doing substantial work on the code.  Half the time it's just because I
need to look up someone's e-mail address.

> Tell me something Ted.  Have you in the last 5 years or
> so done any work in the kernel outside of fs or modified
> files outside of fs when fs structures weren't changed?

> Are you representative of the typical user of a script like
> get_maintainer or checkpatch?  Does it matter that much?

I've personally always thought of get_maintainer as being more useful
for more experienced developers since you have to have a reasonable idea
of what it's giving you to be able to parse the output effectively.
--
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/