From: Joe Perches <joe@perches.com>
To: Ryan Mallon <rmallon@gmail.com>
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 20:11:52 -0700 [thread overview]
Message-ID: <1307675512.20439.2.camel@Joe-Laptop> (raw)
In-Reply-To: <4DF189F2.3040009@gmail.com>
On Fri, 2011-06-10 at 13:05 +1000, Ryan Mallon wrote:
> 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.
I agree.
> 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?
It's the git commit.
get_maintainer uses the name and address in the first seen
commit matching on the full name where possible.
You can override this with --noremove-duplicates
$ ./scripts/get_maintainer.pl --noremove-duplicates -f drivers/power/ds2782_battery.c
Anton Vorontsov <cbouatmailru@gmail.com> (commit_signer:4/5=80%)
Ryan Mallon <ryan@bluewatersys.com> (commit_signer:3/5=60%)
Andrew Morton <akpm@linux-foundation.org> (commit_signer:1/5=20%)
Peter Huewe <peterhuewe@gmx.de> (commit_signer:1/5=20%)
Mike Rapoport <mike@compulab.co.il> (commit_signer:1/5=20%)
linux-kernel@vger.kernel.org (open list)
next prev parent reply other threads:[~2011-06-10 3:11 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 [this message]
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
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=1307675512.20439.2.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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox