From: joe@perches.com (Joe Perches)
To: linux-arm-kernel@lists.infradead.org
Subject: whoever is using ymiao3@marvell.com please stop it
Date: Tue, 26 Jan 2010 09:10:17 -0800 [thread overview]
Message-ID: <1264525817.30778.139.camel@Joe-Laptop.home> (raw)
In-Reply-To: <20100126113534.GF20792@pengutronix.de>
On Tue, 2010-01-26 at 12:35 +0100, Uwe Kleine-K?nig wrote:
> On Tue, Jan 26, 2010 at 05:23:18AM +0000, Ben Dooks wrote:
> > On Tue, Jan 26, 2010 at 09:30:39AM +0800, Eric Miao wrote:
> > > That's mine original email, and is invalid now. Everyone please stop using it.
> I already run into that several times as I frequently use
> scripts/get_maintainer.pl. IMHO we need a mechanism to deprecate email
> addresses, preferably using .mailmap as data source.
As is, I think it's not much of a problem.
People move around and email addresses become invalid.
Over short periods of time, these problems are resolved
without effort or intervention.
scripts/get_maintainer.pl uses first MAINTAINERS patterns
and maintainer name/address, then git history. The most
recent git name/address combination is used and multiple
address are ignored by default.
If multiple people with identical names are contributing,
a flag --noremove-duplicates exists to stop name/address
merging.
http://lkml.org/lkml/2009/8/5/518
> I'd suggest to check if the address is listed in .mailmap and use the
> first entry for that person. This would need some work to adapt
> .mailmap, as .mailmap mainly collects wrong entries.
Make sure you adapt git as well.
One thing you could do would be to update
scripts/get_maintainer.pl to scan all MAINTAINERS sections
for a matching name and use that address if it differs from
git log history.
That could update the case where the person has a MAINTAINERS
entry, is not a listed maintainer for a particular file and
had last submitted patches for that file using an old/invalid
address.
I will not be submitting such a patch.
prev parent reply other threads:[~2010-01-26 17:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-25 1:40 whoever is using ymiao3@marvell.com please stop it Ben Dooks
2010-01-26 1:30 ` Eric Miao
2010-01-26 5:23 ` Ben Dooks
2010-01-26 11:35 ` Uwe Kleine-König
2010-01-26 11:59 ` Mark Brown
2010-01-26 17:10 ` 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=1264525817.30778.139.camel@Joe-Laptop.home \
--to=joe@perches.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).