linux-kernel - Re: [PATCH] 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] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 10 Sep 2010 12:22:13 +0200
From:	Florian Mickler <florian@...kler.org>
To:	Joe Perches <joe@...ches.com>
Cc:	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	"Stephen Hemminger (role:commit_signer)" <shemminger@...tta.com>,
	"Wolfram Sang (role:commit_signer)" <w.sang@...gutronix.de>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] get_maintainer.pl: append reason for cc to the name by
 default

On Fri, 10 Sep 2010 03:04:26 -0700
Joe Perches <joe@...ches.com> wrote:

> On Fri, 2010-09-10 at 10:53 +0100, Mark Brown wrote:
> > On Fri, Sep 10, 2010 at 02:42:47AM -0700, Joe Perches wrote:
> > > As the coverage of file patterns in MAINTAINERS is
> > > now pretty good, the --git results are less useful.
> > It's pretty good for subsystems and PC drivers but for embedded stuff it
> > is much more patchy and fairly unlikely to find someone who actually
> > knows about the specific hardware.
> 
> Especially not so good for ARM stuff.
> 
> It'd be great if the ARM/embedded folk would spend
> some effort improving the MAINTAINERS file pattern
> coverage.

hm.. not likely to happen.

> One possible improvement that get_maintainers could
> add is to [optionally] CC the author of the first
> commit when there's no listed maintainer.
> 

I don't think the first commit has any special significance 
in general. 

--
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/