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

Message-ID: <20100927154441.GE3602@thunk.org>
Date:	Mon, 27 Sep 2010 11:44:41 -0400
From:	Ted Ts'o <tytso@....edu>
To:	Florian Mickler <florian@...kler.org>
Cc:	Joe Perches <joe@...ches.com>,
	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 04:57:48PM +0200, Florian Mickler wrote:
> 
> Would in essence have the same effect, but I think it's slightly better
> to have some shorter tags in the mail addresses, as I expect them to
> actually show up on lkml quite a bit.

What if there are no tags on mail addresses that come from the
MAINTAINERS file, but only tags on the mail addresses that come from
guessing wildly based on git sign-offs?  People should just be looking
in the MAINTAINERS file, after all, and I don't think that's something
that needs an explanation.

The thing that needs explanation is when someone like Steve Hemminger
gets cc'ed on a patch for fs/ext4/acl.c, which really makes no sense
at all, where you desperately need some kind of tag:

shemminger@...tta.com (Wild guess using get_maintainer.pl --git)

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