From: John Snow <jsnow@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
Eric Blake <eblake@redhat.com>,
qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org
Subject: Re: [PATCH] bitmaps: Add myself as maintainer
Date: Thu, 14 May 2020 01:08:14 -0400 [thread overview]
Message-ID: <ad142f8d-8d10-1909-c1d4-7ca8441ab3ba@redhat.com> (raw)
In-Reply-To: <30070988-e0da-00f2-3780-d4fae816b589@virtuozzo.com>
On 5/14/20 12:49 AM, Vladimir Sementsov-Ogievskiy wrote:
> 13.05.2020 23:24, John Snow wrote:
>>
>>
>> On 5/13/20 10:14 AM, Eric Blake wrote:
>>> 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
>>>
>>
>> I'd also like to point out that I wouldn't mind if Vladimir became an
>> official maintainer, but I can't remember if he wanted the title when we
>> last spoke at KVM Forum.
>
> Actually, it would be nice, I'd glad to get it, thanks :)
> I can send a separate patch, or we may s/R/M/ in this one?
>
That would be very good!
I'd be quite happy to be demoted to reviewer; it's about all the time
I've been truthfully able to give lately.
(I won't speak for Eric!)
--js
next prev parent reply other threads:[~2020-05-14 5:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 14:14 [PATCH] bitmaps: Add myself as maintainer Eric Blake
2020-05-13 19:00 ` 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 [this message]
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=ad142f8d-8d10-1909-c1d4-7ca8441ab3ba@redhat.com \
--to=jsnow@redhat.com \
--cc=eblake@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).