All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Ryan Mallon <rmallon@gmail.com>, Florian Mickler <florian@mickler.org>
Cc: 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
Subject: Re: [PATCH trival/tree-wide] Change Ryan Mallon's email address across the kernel
Date: Thu, 09 Jun 2011 21:14:48 -0700	[thread overview]
Message-ID: <1307679288.20439.15.camel@Joe-Laptop> (raw)
In-Reply-To: <4DF19565.9070601@gmail.com>

On Fri, 2011-06-10 at 13:54 +1000, Ryan Mallon wrote:
> Okay, so what is the preferred solution. Do I leave the old address in 
> the files and add MAINTAINERS entries for everything with my correct 
> address, or do I delete my email address (but leave my name) in all of 
> the files?

Another option is to add an entry in .mailmap for
your correct new and incorrect old addresses.

diff --git a/.mailmap b/.mailmap
index 353ad56..218765d 100644
--- a/.mailmap
+++ b/.mailmap
@@ -95,6 +95,7 @@ Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
 Rémi Denis-Courmont <rdenis@simphalempin.com>
 Rudolf Marek <R.Marek@sh.cvut.cz>
 Rui Saraiva <rmps@joel.ist.utl.pt>
+Ryan Mallon <rmallon@gmail.com> <ryan@bluewatersys.com>
 Sachin P Sant <ssant@in.ibm.com>
 Sam Ravnborg <sam@mars.ravnborg.org>
 Sascha Hauer <s.hauer@pengutronix.de>


This will only work after get_maintainers is patched
to correctly parse the .mailmap entries that use this form.

I'll chat with Florian to correct this.

cheers, Joe


  reply	other threads:[~2011-06-10  4:14 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 [this message]
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

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=1307679288.20439.15.camel@Joe-Laptop \
    --to=joe@perches.com \
    --cc=andre@bluewatersys.com \
    --cc=avictor.za@gmail.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=cbou@mail.ru \
    --cc=dwmw2@infradead.org \
    --cc=florian@mickler.org \
    --cc=hsweeten@visionengravers.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.