From: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
To: qemu-devel@nongnu.org, Laurent Vivier <laurent@vivier.eu>
Cc: qemu-trivial@nongnu.org, Hyman Huang <huangy81@chinatelecom.cn>,
Pan Nengyuan <pannengyuan@huawei.com>,
Haibin Zhang <haibinzhang@tencent.com>,
Alex Chen <alex.chen@huawei.com>
Subject: Re: [PATCH-for-6.2 v2] .mailmap: Fix more contributor entries
Date: Thu, 4 Nov 2021 23:06:52 +0100 [thread overview]
Message-ID: <fec0423b-8ef7-7a76-6827-1ebb6c69db1a@amsat.org> (raw)
In-Reply-To: <530b7d0e-9290-c78a-df50-7ef297dbf0b6@amsat.org>
Ping for 6.2? (Patch fully reviewed/acked by affected contributors).
On 11/1/21 11:22, Philippe Mathieu-Daudé wrote:
> Can this patch go via the Trivial tree?
>
> On 10/27/21 06:32, Philippe Mathieu-Daudé wrote:
>> These authors have some incorrect author email field.
>>
>> Acked-by: Pan Nengyuan <pannengyuan@huawei.com>
>> Reviewed-by: Alex Chen <alex.chen@huawei.com>
>> Reviewed-by: Hyman Huang <huangy81@chinatelecom.cn>
>> Reviewed-by: Haibin Zhang <haibinzhang@tencent.com>
>> Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
>> ---
>> Patch fully reviewed/acked.
>> ---
>> .mailmap | 4 ++++
>> 1 file changed, 4 insertions(+)
>>
>> diff --git a/.mailmap b/.mailmap
>> index f029d1c21fe..8beb2f95ae2 100644
>> --- a/.mailmap
>> +++ b/.mailmap
>> @@ -69,6 +69,7 @@ Yongbok Kim <yongbok.kim@mips.com> <yongbok.kim@imgtec.com>
>> # git author config, or had utf8/latin1 encoding issues.
>> Aaron Lindsay <aaron@os.amperecomputing.com>
>> Alexey Gerasimenko <x1917x@gmail.com>
>> +Alex Chen <alex.chen@huawei.com>
>> Alex Ivanov <void@aleksoft.net>
>> Andreas Färber <afaerber@suse.de>
>> Bandan Das <bsd@redhat.com>
>> @@ -99,9 +100,11 @@ Gautham R. Shenoy <ego@in.ibm.com>
>> Gautham R. Shenoy <ego@linux.vnet.ibm.com>
>> Gonglei (Arei) <arei.gonglei@huawei.com>
>> Guang Wang <wang.guang55@zte.com.cn>
>> +Haibin Zhang <haibinzhang@tencent.com>
>> Hailiang Zhang <zhang.zhanghailiang@huawei.com>
>> Hanna Reitz <hreitz@redhat.com> <mreitz@redhat.com>
>> Hervé Poussineau <hpoussin@reactos.org>
>> +Hyman Huang <huangy81@chinatelecom.cn>
>> Jakub Jermář <jakub@jermar.eu>
>> Jakub Jermář <jakub.jermar@kernkonzept.com>
>> Jean-Christophe Dubois <jcd@tribudubois.net>
>> @@ -135,6 +138,7 @@ Nicholas Thomas <nick@bytemark.co.uk>
>> Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>
>> Orit Wasserman <owasserm@redhat.com>
>> Paolo Bonzini <pbonzini@redhat.com>
>> +Pan Nengyuan <pannengyuan@huawei.com>
>> Pavel Dovgaluk <dovgaluk@ispras.ru>
>> Pavel Dovgaluk <pavel.dovgaluk@gmail.com>
>> Pavel Dovgaluk <Pavel.Dovgaluk@ispras.ru>
>>
>
next prev parent reply other threads:[~2021-11-04 22:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 4:32 [PATCH v2] .mailmap: Fix more contributor entries Philippe Mathieu-Daudé
2021-11-01 10:22 ` Philippe Mathieu-Daudé
2021-11-04 22:06 ` Philippe Mathieu-Daudé [this message]
2021-11-05 12:03 ` [PATCH-for-6.2 " Laurent Vivier
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=fec0423b-8ef7-7a76-6827-1ebb6c69db1a@amsat.org \
--to=f4bug@amsat.org \
--cc=alex.chen@huawei.com \
--cc=haibinzhang@tencent.com \
--cc=huangy81@chinatelecom.cn \
--cc=laurent@vivier.eu \
--cc=pannengyuan@huawei.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).