All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: Eric Blake <eblake@redhat.com>,
	Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
	qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org
Subject: Re: [PATCH] bitmaps: Add myself as maintainer
Date: Thu, 14 May 2020 10:25:33 -0400	[thread overview]
Message-ID: <7ba5c8af-f2cd-9e13-ba3e-f40f6ff6122b@redhat.com> (raw)
In-Reply-To: <962f8c29-6b42-ea7c-cdf9-ad63288da955@redhat.com>



On 5/14/20 9:52 AM, Eric Blake wrote:
> On 5/14/20 12:08 AM, John Snow wrote:
>>
>>
>> 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>
>>>>>
>>>>> ---
> 
>>>>>    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!)
> 
> I can post a v2 that produces the following results:
> 
> M: Vladimir
> M: Eric
> R: John
> 
> Does that sound reasonable?
> 
> 

Yeah, I will approve it. I want to help as much as I can, but I don't
want to artificially limit the rate of development here as I fear I have
been.

--js



  reply	other threads:[~2020-05-14 14:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-13 14:14 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
2020-05-14 13:52       ` Eric Blake
2020-05-14 14:25         ` John Snow [this message]
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=7ba5c8af-f2cd-9e13-ba3e-f40f6ff6122b@redhat.com \
    --to=jsnow@redhat.com \
    --cc=eblake@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=vsementsov@virtuozzo.com \
    --subject='Re: [PATCH] bitmaps: Add myself as maintainer' \
    /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

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.