From: Eric Blake <eblake@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Jason Wang <jasowang@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL 0/2] Net patches
Date: Mon, 26 Mar 2018 13:18:16 -0500 [thread overview]
Message-ID: <8e877bbc-a0d9-8d6b-54c0-1831d340e1e9@redhat.com> (raw)
In-Reply-To: <CAFEAcA-SuZ-aEY5aFpqdrjfGeNH+FoLz5vCxf4crJJdiO6w1jw@mail.gmail.com>
On 03/26/2018 11:59 AM, Peter Maydell wrote:
> On 26 March 2018 at 17:54, Eric Blake <eblake@redhat.com> wrote:
>> Hmm, on re-reading that, I wonder if shortlog will do the right thing when a
>> .mailmap entry exists. I'm trying to make sure we don't have to go
>> lower-level with use of 'git log --format=%ae' (vs. --format=%aE and/or log
>> --use-mailmap).
>>
>> /me goes and experiments with:
>>
>> +Julia Suvorova <<jusual@mail.ru> Julia Suvorova via Qemu-devel
>> <qemu-devel@nongnu.org>
>
> Your mailmap change above seems to have a stray extra '<' in it --
> was that added by the mailing list server, or is it in the original?
D'oh, extra < in my playground. Thankfully, removing it, and trying
again, finds the same results: 'git shortlog
--author=qemu-devel@nongnu.org' finds all Author: entries that were
originally spelled with the list address, even if a .mailmap entry would
rewrite it during 'git log --use-mailmap'.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2018-03-26 18:18 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-26 7:00 [Qemu-devel] [PULL 0/2] Net patches Jason Wang
2018-03-26 7:00 ` [Qemu-devel] [PULL 1/2] virtio_net: flush uncompleted TX on reset Jason Wang
2018-03-26 7:00 ` [Qemu-devel] [PULL 2/2] net/vde: print error on vde_open() failure Jason Wang
2018-03-26 12:13 ` Philippe Mathieu-Daudé
2018-03-26 14:20 ` Eric Blake
2018-03-26 12:40 ` [Qemu-devel] [PULL 0/2] Net patches no-reply
2018-03-26 13:14 ` Peter Maydell
2018-03-26 14:23 ` Eric Blake
2018-03-26 16:12 ` Peter Maydell
2018-03-26 16:54 ` Eric Blake
2018-03-26 16:59 ` Peter Maydell
2018-03-26 18:18 ` Eric Blake [this message]
2018-03-26 16:29 ` Eric Blake
-- strict thread matches above, loose matches on Subject: below --
2018-07-20 0:45 Jason Wang
2018-07-20 10:08 ` Peter Maydell
2017-06-07 3:34 Jason Wang
2017-06-07 4:31 ` no-reply
2017-06-07 6:49 ` Jason Wang
2017-06-07 10:55 ` Peter Maydell
2017-03-31 1:15 Jason Wang
2017-03-31 10:09 ` Peter Maydell
2016-08-22 8:09 Jason Wang
2016-08-22 10:03 ` Peter Maydell
2016-08-18 5:40 Jason Wang
2016-08-18 10:22 ` Peter Maydell
2013-09-20 17:53 Stefan Hajnoczi
2013-06-07 13:54 Stefan Hajnoczi
2013-06-17 21:17 ` Anthony Liguori
2013-05-24 14:38 Stefan Hajnoczi
2013-06-17 21:18 ` Anthony Liguori
2013-05-03 11:57 Stefan Hajnoczi
2013-04-08 12:42 Stefan Hajnoczi
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=8e877bbc-a0d9-8d6b-54c0-1831d340e1e9@redhat.com \
--to=eblake@redhat.com \
--cc=jasowang@redhat.com \
--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 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.