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:	Tue, 14 Jun 2011 09:05:24 +1000
From:	Ryan Mallon <rmallon@...il.com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
CC:	Paul Mundt <lethal@...ux-sh.org>, linux-kernel@...r.kernel.org,
	Andre Renaud <andre@...ewatersys.com>,
	H Hartley Sweeten <hsweeten@...ionengravers.com>,
	Russell King <linux@....linux.org.uk>,
	Nicolas Ferre <nicolas.ferre@...el.com>,
	Andrew Victor <avictor.za@...il.com>,
	David Woodhouse <dwmw2@...radead.org>,
	Anton Vorontsov <cbou@...l.ru>, Liam Girdwood <lrg@...com>,
	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	trivial@...nel.org, jj@...osbits.net
Subject: Re: [PATCH trival/tree-wide] Change Ryan Mallon's email address across
 the kernel

On 10/06/11 18:56, Alan Cox wrote:
> On Fri, 10 Jun 2011 11:55:49 +0900
> Paul Mundt<lethal@...ux-sh.org>  wrote:
>
>> On Fri, Jun 10, 2011 at 09:12:50AM +1000, Ryan Mallon wrote:
>>> I no longer work at Bluewater Systems. Update my email address accordingly.
>>>
>> Is this sort of churn really necessary?
> Yes - stale email addresses cause all sorts of problems, particularly if
> in the future the address is re-used in the company. It also causes
> confusion over who owns and maintains stuff because it's never obvious
> whether the resolution of an unknown address is
>
> A.	'user has moved on, follow the user'
>
> B.	'user has moved on, company probably has someone else assigned
> 	 to it'

Okay, so there seem to be a number of different opinions on this. I 
would really like some solution for this so it can go into 3.0. The 
options I see are:

a) My original patch
b) My original patch, but delete email address in .[ch] files rather 
than change it
c) Entry in .mailmap (will this work for 3.0?)
d) Add MAINTAINERS entries for each of the files which have my email 
address in them
e) Some combination of the above

Is there a preferred option? Who (Linus?) do I need to Cc to get this 
included for 3.0?

Thanks,
~Ryan

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ