From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Andrey Drobyshev" <andrey.drobyshev@virtuozzo.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>
Subject: [PULL 01/15] mailmap: Fix Andrey Drobyshev author email
Date: Thu, 5 Oct 2023 13:44:48 -0500 [thread overview]
Message-ID: <20231005184447.682556-18-eblake@redhat.com> (raw)
In-Reply-To: <20231005184447.682556-17-eblake@redhat.com>
From: Andrey Drobyshev <andrey.drobyshev@virtuozzo.com>
This fixes authorship of commits 2848289168, 52b10c9c0c as the mailing
list rewrote the "From:" field in the corresponding patches. See commit
3bd2608db7 ("maint: Add .mailmap entries for patches claiming list
authorship") for explanation.
Signed-off-by: Andrey Drobyshev <andrey.drobyshev@virtuozzo.com>
Message-ID: <20230926102801.512107-1-andrey.drobyshev@virtuozzo.com>
Reviewed-by: Eric Blake <eblake@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
Signed-off-by: Eric Blake <eblake@redhat.com>
---
.mailmap | 1 +
1 file changed, 1 insertion(+)
diff --git a/.mailmap b/.mailmap
index 64ef9f4de6f..04a7feb005b 100644
--- a/.mailmap
+++ b/.mailmap
@@ -46,6 +46,7 @@ Ian McKellar <ianloic@google.com> Ian McKellar via Qemu-devel <qemu-devel@nongnu
Julia Suvorova <jusual@mail.ru> Julia Suvorova via Qemu-devel <qemu-devel@nongnu.org>
Justin Terry (VM) <juterry@microsoft.com> Justin Terry (VM) via Qemu-devel <qemu-devel@nongnu.org>
Stefan Weil <sw@weilnetz.de> Stefan Weil via <qemu-devel@nongnu.org>
+Andrey Drobyshev <andrey.drobyshev@virtuozzo.com> Andrey Drobyshev via <qemu-block@nongnu.org>
# Next, replace old addresses by a more recent one.
Aleksandar Markovic <aleksandar.qemu.devel@gmail.com> <aleksandar.markovic@mips.com>
--
2.41.0
next prev parent reply other threads:[~2023-10-05 18:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 18:44 [PULL 00/15] NBD patches through 2023-10-05 Eric Blake
2023-10-05 18:44 ` Eric Blake [this message]
2023-10-05 18:44 ` [PULL 02/15] maint: Tweak comments in mailmap regarding SPF Eric Blake
2023-10-05 18:44 ` [PULL 03/15] mailmap: Fix BALATON Zoltan author email Eric Blake
2023-10-05 18:44 ` [PULL 04/15] nbd/server: Support a request payload Eric Blake
2023-10-05 18:44 ` [PULL 05/15] nbd/server: Prepare to receive extended header requests Eric Blake
2023-10-05 18:44 ` [PULL 06/15] nbd/server: Prepare to send extended header replies Eric Blake
2023-10-05 18:44 ` [PULL 07/15] nbd/server: Support 64-bit block status Eric Blake
2023-10-05 18:44 ` [PULL 08/15] nbd/server: Enable initial support for extended headers Eric Blake
2023-10-05 18:44 ` [PULL 09/15] nbd/client: Plumb errp through nbd_receive_replies Eric Blake
2023-10-05 18:44 ` [PULL 10/15] nbd/client: Initial support for extended headers Eric Blake
2023-10-05 18:44 ` [PULL 11/15] nbd/client: Accept 64-bit block status chunks Eric Blake
2023-10-05 18:44 ` [PULL 12/15] nbd/client: Request extended headers during negotiation Eric Blake
2023-10-05 18:45 ` [PULL 13/15] nbd/server: Refactor list of negotiated meta contexts Eric Blake
2023-10-05 18:45 ` [PULL 14/15] nbd/server: Prepare for per-request filtering of BLOCK_STATUS Eric Blake
2023-10-05 18:45 ` [PULL 15/15] nbd/server: Add FLAG_PAYLOAD support to CMD_BLOCK_STATUS Eric Blake
2023-10-10 1:28 ` [PULL 00/15] NBD patches through 2023-10-05 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=20231005184447.682556-18-eblake@redhat.com \
--to=eblake@redhat.com \
--cc=andrey.drobyshev@virtuozzo.com \
--cc=philmd@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.