From: "Andreas Färber" <afaerber@suse.de>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org, patches@linaro.org
Subject: Re: [Qemu-devel] [RFC] Add a .mailmap to map pre-git-conversion authors to friendly names
Date: Fri, 18 Nov 2011 14:30:17 +0100 [thread overview]
Message-ID: <4EC65DE9.7000303@suse.de> (raw)
In-Reply-To: <CAFEAcA_7qaRAsTLooz8j2SwRH_mU0fm6ciKuexXiT4+XsBrq9Q@mail.gmail.com>
Am 17.11.2011 19:10, schrieb Peter Maydell:
> ...nobody cares at all either way? (in which case we should commit
> it for my personal benefit if nothing else ;-))
Had a brief look at it, but didn't check the SVN "email addresses".
I like the idea in general.
> On 26 October 2011 18:36, Peter Maydell <peter.maydell@linaro.org> wrote:
>> Add a .mailmap file so 'git shortlog' can map the unfriendly
>> pre-git-conversion author entries to real names.
>>
>> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
>> ---
>> diff --git a/.mailmap b/.mailmap
>> new file mode 100644
>> index 0000000..6f968d8
>> --- /dev/null
>> +++ b/.mailmap
>> @@ -0,0 +1,20 @@
>> +# This mailmap just translates the weird addresses from the original import into git
>> +# into proper addresses so that they are counted properly in git shortlog output.
>> +#
>> +Aurelien Jarno <aurelien@aurel32.net> aurel32 <aurel32@c046a42c-6fe2-441c-8c8c-71466251a162>
>> +Blue Swirl <blauwirbel@gmail.com> blueswir1 <blueswir1@c046a42c-6fe2-441c-8c8c-71466251a162>
>> +Anthony Liguori <aliguori@us.ibm.com> aliguori <aliguori@c046a42c-6fe2-441c-8c8c-71466251a162>
>> +Edgar E. Iglesias <edgar.iglesias@gmail.com> edgar_igl <edgar_igl@c046a42c-6fe2-441c-8c8c-71466251a162>
>> +malc <av1474@comtv.ru> malc <malc@c046a42c-6fe2-441c-8c8c-71466251a162>
>> +Paul Brook <paul@codesourcery.com> pbrook <pbrook@c046a42c-6fe2-441c-8c8c-71466251a162>
>> +Andrzej Zaborowski <balrog@zabor.org> balrog <balrog@c046a42c-6fe2-441c-8c8c-71466251a162>
You should probably at least cc (if not get acks from) all the persons
listed above.
Anthony is using two; Andrzej four and a different one lately.
>> +Thiemo Seufer <ths@networkno.de> ths <ths@c046a42c-6fe2-441c-8c8c-71466251a162>
>> +#
>> +# Weird addresses with no translation because they have made no commits since the
>> +# switchover to git:
>> +# bellard <bellard@c046a42c-6fe2-441c-8c8c-71466251a162>
Fabrice Bellard <fabrice@bellard.org> (cf. bellard.org)
>> +# j_mayer <j_mayer@c046a42c-6fe2-441c-8c8c-71466251a162>
Jocelyn Mayer <l_indien@magic.fr> (cf. OpenHack'Ware sources)
>> +#
>> +# There is also a:
>> +# (no author) <(no author)@c046a42c-6fe2-441c-8c8c-71466251a162>
>> +# for the cvs2svn initialization commit e63c3dc74bf.
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2011-11-18 13:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-26 17:36 [Qemu-devel] [RFC] Add a .mailmap to map pre-git-conversion authors to friendly names Peter Maydell
2011-11-17 18:10 ` Peter Maydell
2011-11-17 19:15 ` Anthony Liguori
2011-11-18 13:30 ` Andreas Färber [this message]
2011-11-18 14:00 ` Peter Maydell
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=4EC65DE9.7000303@suse.de \
--to=afaerber@suse.de \
--cc=patches@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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).