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]

Message-ID: <1284111767.1783.35.camel@Joe-Laptop>
Date:	Fri, 10 Sep 2010 02:42:47 -0700
From:	Joe Perches <joe@...ches.com>
To:	florian@...kler.org
Cc:	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, 2010-09-10 at 11:33 +0200, florian@...kler.org wrote:
> The script get_maintainer.pl is a very useful tool for deploying changes
> made to the kernel. Among others it searches not only the MAINTAINERS
> file but also the git history for people to send patches to.\
[]
> By appending a  a note of the reason for the cc in the name, the reason
> becomes clear and the receiving side is relieved from feeling obliged to
> check the patch  while the sending side has a chance to adapt the
> cc'list to their liking.

I don't like reading annotated email names myself.

As the coverage of file patterns in MAINTAINERS is
now pretty good, the --git results are less useful.

I'd much rather turn off --git as a default, or change
get_maintainers to add git signers only when there's no
specifically listed maintainer for a particular file.


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