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: <20100927165748.354742f2@schatten.dmk.lab>
Date:	Mon, 27 Sep 2010 16:57:48 +0200
From:	Florian Mickler <florian@...kler.org>
To:	Joe Perches <joe@...ches.com>
Cc:	Ted Ts'o <tytso@....edu>,
	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 Sun, 26 Sep 2010 11:52:05 -0700
Joe Perches <joe@...ches.com> wrote:

> 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.
> > 
> > This can be unexpected for the receiving side and can and does provoke
> > sometimes anger because it is not easy to determine if the sender did
> > explicitly put the receiving side on the cc list, or if they just
> > trolled the tree. The receiving side, if not used to be cc'd on many
> > things will check the patch, spend time investigating what the heck they
> > were cc'd just to realize, that there was no special reason.
> > 
> > As get_maintainer.pl is frequently used by kernel newcomers who _can_
> > not know whom to cc by themself, this anger then comes as a surprise for them
> > and definitely puts them in an awkward position.
> > 
> > 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.
> > 
> > But the most useful aspect of this is, IMHO, that it makes it transparent who
> > just used get_maintainer.pl as a shortcut to increase his own
> > patch-throughput or who really put an effort in finding or editing the
> > cc'list to their likings.
> 
> How about making --rolestats the default and adding a --nodecorate
> option default off?
> 
> This would mean that any current script that expects bare email
> addresses would need to add --nodecorate to get the old behavior.
> 

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.

Regards,
Flo
--
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/