All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ryan Mallon <rmallon@gmail.com>
To: Paul Mundt <lethal@linux-sh.org>
Cc: Joe Perches <joe@perches.com>,
	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: Fri, 10 Jun 2011 13:54:13 +1000	[thread overview]
Message-ID: <4DF19565.9070601@gmail.com> (raw)
In-Reply-To: <20110610035115.GF26006@linux-sh.org>

On 10/06/11 13:51, Paul Mundt wrote:
> On Fri, Jun 10, 2011 at 01:31:54PM +1000, Ryan Mallon wrote:
>> On 10/06/11 13:24, Joe Perches wrote:
>>> On Fri, 2011-06-10 at 13:13 +1000, Ryan Mallon wrote:
>>>> On 10/06/11 13:11, Joe Perches wrote:
>>>>> 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?
>>>>> get_maintainer uses the name and address in the first seen
>>>>> commit matching on the full name where possible.
>>>> Okay, what is the correct fix then so that people get the right email
>>>> address for me?
>>> I believe updating the MAINTAINERS file and
>>> authoring and committing patches that take
>>> your email address out of files works well.
>> If I strip my email address, but leave my name and copyright in the
>> files the patch will have the same amount of churn right?
>>
> Not necessarily. You can leave the copyright bits intact but simply
> update (or strip out) the address from the MODULE_AUTHOR part so people
> still get the proper data from modinfo and so on. There are many people
> with non-working email addresses in copyright statements tree-wide, so
> there's certainly a precedent for it. It's also a motivator for not
> bothering with inlining the email address in the future, unless it's to
> avoid ambiguity (ie, a work done on behalf of an employer, who retains
> all rights).
>
> If there are files that you have authored but get_maintainers is
> groveling the commits and using your old address, you can preempt this by
> simply adding a MAINTAINERS entry with the appropriate file pattern, too.

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?

~Ryan



  reply	other threads:[~2011-06-10  3:54 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 [this message]
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=4DF19565.9070601@gmail.com \
    --to=rmallon@gmail.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=joe@perches.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=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.