From: Max Reitz <mreitz@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
qemu-block@nongnu.org
Cc: kwolf@redhat.com, jsnow@redhat.com, qemu-devel@nongnu.org
Subject: Re: [PATCH] MAINTAINERS: suggest myself as co-maintainer for Block Jobs
Date: Thu, 28 Jan 2021 17:22:00 +0100 [thread overview]
Message-ID: <a676b450-4118-7686-3867-438a4d30fb91@redhat.com> (raw)
In-Reply-To: <20210128144144.27617-1-vsementsov@virtuozzo.com>
On 28.01.21 15:41, Vladimir Sementsov-Ogievskiy wrote:
> I'm developing Qemu backup for several years, and finally new backup
> architecture, including block-copy generic engine and backup-top filter
> landed upstream, great thanks to reviewers and especially to
> Max Reitz!
>
> I also have plans of moving other block-jobs onto block-copy, so that
> we finally have one generic block copying path, fast and well-formed.
>
> So, now I suggest to bring all parts of backup architecture into
> "Block Jobs" subsystem (actually, aio_task is shared with qcow2 and
> qemu-co-shared-resource can be reused somewhere else, but I'd keep an
> eye on them in context of block-jobs) and add myself as co-maintainer.
>
> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
> ---
> MAINTAINERS | 9 +++++++++
> 1 file changed, 9 insertions(+)
Great! :)
Reviewed-by: Max Reitz <mreitz@redhat.com>
prev parent reply other threads:[~2021-01-28 16:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 14:41 [PATCH] MAINTAINERS: suggest myself as co-maintainer for Block Jobs Vladimir Sementsov-Ogievskiy
2021-01-28 15:09 ` Markus Armbruster
2021-01-28 15:28 ` John Snow
2021-02-01 11:03 ` Vladimir Sementsov-Ogievskiy
2021-02-01 13:50 ` Alex Bennée
2021-02-01 14:35 ` Daniel P. Berrangé
2021-02-01 14:50 ` Kevin Wolf
2021-02-01 16:20 ` Vladimir Sementsov-Ogievskiy
2021-02-01 16:58 ` Kevin Wolf
2021-02-01 17:08 ` Vladimir Sementsov-Ogievskiy
2021-02-03 8:22 ` Vladimir Sementsov-Ogievskiy
2021-02-03 15:57 ` John Snow
2021-01-28 16:22 ` Max Reitz [this message]
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=a676b450-4118-7686-3867-438a4d30fb91@redhat.com \
--to=mreitz@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@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).