From: Joe Perches <joe@perches.com>
To: Ryan Mallon <rmallon@gmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Paul Mundt <lethal@linux-sh.org>,
linux-kernel@vger.kernel.org,
Andre Renaud <andre@bluewatersys.com>,
H Hartley Sweeten <hsweeten@visionengravers.com>,
Russell King <linux@arm.linux.org.uk>,
Nicolas Ferre <nicolas.ferre@atmel.com>,
Andrew Victor <avictor.za@gmail.com>,
David Woodhouse <dwmw2@infradead.org>,
Anton Vorontsov <cbou@mail.ru>, Liam Girdwood <lrg@ti.com>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
trivial@kernel.org, jj@chaosbits.net,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH trival/tree-wide] Change Ryan Mallon's email address across the kernel
Date: Mon, 13 Jun 2011 16:15:56 -0700 [thread overview]
Message-ID: <1308006956.26699.52.camel@Joe-Laptop> (raw)
In-Reply-To: <4DF697B4.6080000@gmail.com>
On Tue, 2011-06-14 at 09:05 +1000, Ryan Mallon wrote:
> On 10/06/11 18:56, Alan Cox wrote:
> > On Fri, 10 Jun 2011 11:55:49 +0900
> > Paul Mundt<lethal@linux-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?)
It will if Andrew Morton/Linus picks up my patch.
> 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?
My preferred combination is b and c.
If you're European, maybe a and c is best.
prev parent reply other threads:[~2011-06-13 23:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-09 23:12 [PATCH trival/tree-wide] Change Ryan Mallon's email address across the kernel Ryan Mallon
2011-06-10 0:28 ` H Hartley Sweeten
2011-06-10 0:50 ` Ryan Mallon
2011-06-10 2:55 ` Paul Mundt
2011-06-10 3:05 ` Ryan Mallon
2011-06-10 3:11 ` Joe Perches
2011-06-10 3:13 ` Ryan Mallon
2011-06-10 3:24 ` Joe Perches
2011-06-10 3:31 ` Ryan Mallon
2011-06-10 3:51 ` Paul Mundt
2011-06-10 3:54 ` Ryan Mallon
2011-06-10 4:14 ` Joe Perches
2011-06-10 10:37 ` [PATCH] get_maintainers.pl: Improve .mailmap parsing Joe Perches
2011-06-10 10:56 ` Florian Mickler
2011-06-10 9:33 ` [PATCH trival/tree-wide] Change Ryan Mallon's email address across the kernel Jesper Juhl
2011-06-10 8:56 ` Alan Cox
2011-06-13 23:05 ` Ryan Mallon
2011-06-13 23:15 ` Joe Perches [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1308006956.26699.52.camel@Joe-Laptop \
--to=joe@perches.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andre@bluewatersys.com \
--cc=avictor.za@gmail.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=cbou@mail.ru \
--cc=dwmw2@infradead.org \
--cc=hsweeten@visionengravers.com \
--cc=jj@chaosbits.net \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=lrg@ti.com \
--cc=nicolas.ferre@atmel.com \
--cc=rmallon@gmail.com \
--cc=trivial@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox