From: Eric Blake <eblake@redhat.com>
To: qemu-devel@nongnu.org
Cc: vsementsov@virtuozzo.com, jsnow@redhat.com, qemu-block@nongnu.org
Subject: [PATCH] bitmaps: Add myself as maintainer
Date: Wed, 13 May 2020 09:14:07 -0500 [thread overview]
Message-ID: <20200513141407.185198-1-eblake@redhat.com> (raw)
Dirty bitmaps are important to incremental backups, including exposure
over NBD where I'm already maintainer. Also, I'm aware that lately I
have been doing as much code/review on bitmaps as John Snow, who is
hoping to scale back on this front.
Signed-off-by: Eric Blake <eblake@redhat.com>
---
This still leaves John as maintainer for: IDE, Floppy, and Block Jobs,
which I did not feel comfortable taking on at this time.
If this patch makes sense, I'm happy to take on my recent 'qemu-img
bitmap' series as my first bitmap-related pull request, once it has
sufficient review.
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 6a8dc1e69d42..f7caf7c0cc7f 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -2002,6 +2002,7 @@ T: git https://repo.or.cz/qemu/armbru.git block-next
Dirty Bitmaps
M: John Snow <jsnow@redhat.com>
+M: Eric Blake <eblake@redhat.com>
R: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
L: qemu-block@nongnu.org
S: Supported
--
2.26.2
next reply other threads:[~2020-05-13 14:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 14:14 Eric Blake [this message]
2020-05-13 19:00 ` [PATCH] bitmaps: Add myself as maintainer Vladimir Sementsov-Ogievskiy
2020-05-13 20:24 ` John Snow
2020-05-14 4:49 ` Vladimir Sementsov-Ogievskiy
2020-05-14 5:08 ` John Snow
2020-05-14 13:52 ` Eric Blake
2020-05-14 14:25 ` John Snow
2020-05-14 17:16 ` Vladimir Sementsov-Ogievskiy
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=20200513141407.185198-1-eblake@redhat.com \
--to=eblake@redhat.com \
--cc=jsnow@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=vsementsov@virtuozzo.com \
/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).