From: "Alex Bennée" <alex.bennee@linaro.org>
To: Aleksandar Markovic <aleksandar.m.mail@gmail.com>
Cc: qemu-trivial@nongnu.org,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/3] mailmap: Clean up
Date: Sat, 24 Aug 2019 08:30:49 +0100 [thread overview]
Message-ID: <87a7bz2f6e.fsf@linaro.org> (raw)
In-Reply-To: <CAL1e-=hvVp4i=s_Wr0iKy5UO7kH6xw3QR0Ms4_v_tobJSM2wRA@mail.gmail.com>
Aleksandar Markovic <aleksandar.m.mail@gmail.com> writes:
> 23.08.2019. 08.13, "Markus Armbruster" <armbru@redhat.com> је написао/ла:
>>
>> Philippe Mathieu-Daudé <philmd@redhat.com> writes:
>>
>> > Trivial cleanup of .mailmap to have a nice 'git shortlog' output.
>> >
>> > Philippe Mathieu-Daudé (3):
>> > mailmap: Reorder by sections
>> > mailmap: Update philmd email address
>> > mailmap: Add many entries to improve 'git shortlog' statistics
>> >
>> > .mailmap | 123 +++++++++++++++++++++++++++++++++++++++++++++++++++----
>> > 1 file changed, 115 insertions(+), 8 deletions(-)
>>
>> Series
>> Reviewed-by: Markus Armbruster <armbru@redhat.com>
>>
>> However, it increases the difference to contrib/gitdm/aliases.
>
> Alex' initial gitdm effort, as I understood it, was not meant to cover all
> history from 2007 or so, but just to give reasonable statistics for 2018
> (amd future years).
>
> In that light, .mailmap and gitdm aliases do not need to be equivalent.
>
> But perhaps Alex would now want gitdm to be used for all QEMU history? Is
> this desirable?
It would be of interest historically but not something I'd want to spend
a lot of time adding code churn for.
>
> Aleksandar
>
>> I'm just
>> as guilty; my recent "[PATCH 2/2] contrib/gitdm: Add armbru@pond.sub.org
>> to group-map-redhat" updates only that. and not .mailmap.
>>
>> Perhaps we want to keep the two in sync manually. We should then add
>> suitable comments to each file.
>>
>> Could we instead teach gitdm to use .mailmap, and ditch
>> contrib/gitdm/aliases?
>>
>> aliases' format is documented in gitdm's README. Each line maps a
>> non-canonical e-mail address to a canonical one.
>>
>> .mailmap's format is documented in git-shortlog(1). It can do a bit
>> more. Even the common part differs: it has two addresses in different
>> order *boggle*.
>>
--
Alex Bennée
prev parent reply other threads:[~2019-08-24 7:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-22 23:09 [Qemu-devel] [PATCH 0/3] mailmap: Clean up Philippe Mathieu-Daudé
2019-08-22 23:09 ` [Qemu-devel] [PATCH 1/3] mailmap: Reorder by sections Philippe Mathieu-Daudé
2019-08-23 9:37 ` Aleksandar Markovic
2019-08-22 23:09 ` [Qemu-devel] [PATCH 2/3] mailmap: Update philmd email address Philippe Mathieu-Daudé
2019-08-23 9:38 ` Aleksandar Markovic
2019-08-22 23:09 ` [Qemu-devel] [PATCH 3/3] mailmap: Add many entries to improve 'git shortlog' statistics Philippe Mathieu-Daudé
2019-08-23 9:44 ` Aleksandar Markovic
2019-08-23 12:37 ` Philippe Mathieu-Daudé
2019-08-23 6:13 ` [Qemu-devel] [PATCH 0/3] mailmap: Clean up Markus Armbruster
2019-08-23 23:49 ` Aleksandar Markovic
2019-08-24 7:30 ` Alex Bennée [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=87a7bz2f6e.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=aleksandar.m.mail@gmail.com \
--cc=armbru@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).