whoever is using [email protected] please stop it
Getting bounces for ymiao3 at marvell.com from marvell.com after replying to the platform device changes from Uwe Kleine-K???i
Signature · 4 lines
Ben Q: What's a light-year? A: One-third less calories than a regular year.
That's mine original email, and is invalid now. Everyone please stop using it.
Thanks and sorry to bother.
- eric
Quoted 15 lines · Ben Dooks
Getting bounces for ymiao3 at marvell.com from marvell.com after replying to the platform device changes from Uwe Kleine-K???i
--
BenQ: ? ? ?What's a light-year?
A: ? ? ?One-third less calories than a regular year._______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel at lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Quoted 4 lines · Eric Miao
That's mine original email, and is invalid now. Everyone please stop using it.
Thanks and sorry to bother.
- eric
Hmm, somehow it got insetred into the last email I sent, as I got a bounce even though it wasn't aparently to that address.
Quoted 16 lines · Ben Dooks
Quoted 15 lines
Getting bounces for ymiao3 at marvell.com from marvell.com after replying to the platform device changes from Uwe Kleine-K???i
--
BenQ: ? ? ?What's a light-year?
A: ? ? ?One-third less calories than a regular year._______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel at lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
Signature · 5 lines
-- Ben Q: What's a light-year? A: One-third less calories than a regular year.
Hello,
Quoted 2 lines · Ben Dooks
Quoted 1 line · Eric Miao
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. Other addresses that would need similar handling are (at least):
12o3l at tiscali.nl -> roel.kluin at gmail.com damm at igel.co.jp -> damm at opensource.se eric.miao at marvell.com -> eric.y.miao at gmail.com jarkko.nikula at nokia.com -> jhnikula at gmail.com pavel at suse.cz -> pavel at ucw.cz spyro at f2s.com -> ian at mnementh.co.uk x0044955 at ti.com -> ??
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.
Best regards
Uwe
Signature · 2 lines
Pengutronix e.K. | Uwe Kleine-K?nig | Industrial Linux Solutions | http://www.pengutronix.de/ |
Quoted 3 lines · Uwe Kleine-K?nig
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.
This breaks when you get multiple people with the same name - I'm not the only Mark Brown for example (though I don't think any others are actually contributing patches). It'd be better to add an explicit mail address rewriting feature (.forward?).
Quoted 6 lines · Uwe Kleine-K?nig
Quoted 2 lines · Ben Dooks
Quoted 1 line · Eric Miao
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
Quoted 3 lines
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.