From: John Snow <jsnow@redhat.com>
To: Eric Blake <eblake@redhat.com>, qemu-devel@nongnu.org
Cc: vsementsov@virtuozzo.com, qemu-block@nongnu.org
Subject: Re: [PATCH v2] bitmaps: Update maintainer
Date: Thu, 14 May 2020 14:59:55 -0400 [thread overview]
Message-ID: <b5f9c802-b6a8-b2b2-f837-25722c10de86@redhat.com> (raw)
In-Reply-To: <20200514180003.325406-1-eblake@redhat.com>
On 5/14/20 2:00 PM, 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
> trying to scale back in order to focus elsewhere; and many of the
> recent patches have come from Vladimir, who is also interested in
> taking on maintainer duties, but would like to start with
> co-maintainership. Therefore, it's time to revamp the ownership of
> this category, as agreed between the three of us.
Great!
>
> Signed-off-by: Eric Blake <eblake@redhat.com>
> ---
>
> v2: further tweak to maintainership, update T: listing
>
> MAINTAINERS | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index d11f3cb97613..ae23062a51ac 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -2001,8 +2001,9 @@ F: qapi/transaction.json
> T: git https://repo.or.cz/qemu/armbru.git block-next
>
> Dirty Bitmaps
> -M: John Snow <jsnow@redhat.com>
> -R: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
> +M: Eric Blake <eblake@redhat.com>
> +M: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
> +R: John Snow <jsnow@redhat.com>
> L: qemu-block@nongnu.org
> S: Supported
> F: include/qemu/hbitmap.h
> @@ -2013,7 +2014,7 @@ F: migration/block-dirty-bitmap.c
> F: util/hbitmap.c
> F: tests/test-hbitmap.c
> F: docs/interop/bitmaps.rst
> -T: git https://github.com/jnsnow/qemu.git bitmaps
> +T: git https://repo.or.cz/qemu/ericb.git bitmaps
>
> Character device backends
> M: Marc-André Lureau <marcandre.lureau@redhat.com>
>
Acked-by: John Snow <jsnow@redhat.com>
Reviewed-by: John Snow <jsnow@redhat.com>
You'll want to work out repo access betwixt yourselves, but I'll leave
that detail for you to work out.
Thank you,
--js
next prev parent reply other threads:[~2020-05-14 19:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-14 18:00 [PATCH v2] bitmaps: Update maintainer Eric Blake
2020-05-14 18:59 ` John Snow [this message]
2020-05-15 5:33 ` Vladimir Sementsov-Ogievskiy
2020-05-15 8:53 ` Kevin Wolf
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=b5f9c802-b6a8-b2b2-f837-25722c10de86@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).