[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4DF189F2.3040009@gmail.com>
Date: Fri, 10 Jun 2011 13:05:22 +1000
From: Ryan Mallon <rmallon@...il.com>
To: Paul Mundt <lethal@...ux-sh.org>
CC: 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
Subject: Re: [PATCH trival/tree-wide] Change Ryan Mallon's email address across
the kernel
On 10/06/11 12:55, Paul Mundt 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? By all means, update your
> MAINTAINERS entry accordingly, but the rest of it is really pretty
> pointless. People are invariably going to consult MAINTAINERS one way or
> another and get the updated value accordingly. For the rest of these you
> are just as well off ripping out the email address completely.
The MAINTAINERS entry for me only cover the arm ep93xx arch. Prior to
this patch, if I do (for example)
./scripts/get_maintainer.pl -f drivers/power/ds2782_battery.c
It gives my old Bluewater email. With this change it gives my gmail
account. Not sure if that is because it extracts the email from the
source or from the git commit? Either way, the patch gets the correct
behaviour for people who send patches using get_maintainer.
~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