All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Cc: qemu-block@nongnu.org, kchamart@redhat.com,
	libvir-list@redhat.com, jsnow@redhat.com,
	xiechanglong.d@gmail.com, qemu-devel@nongnu.org,
	wencongyang2@huawei.com, eblake@redhat.com
Subject: Re: [PATCH v3 0/3] qapi & doc: deprecate drive-backup
Date: Thu, 04 Nov 2021 06:54:42 +0100	[thread overview]
Message-ID: <87a6ikh3dp.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <20211103132912.1977438-1-vsementsov@virtuozzo.com> (Vladimir Sementsov-Ogievskiy's message of "Wed, 3 Nov 2021 14:29:09 +0100")

Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com> writes:

> Hi all!
>
> See 03 commit message for details. 01-02 are preparation docs update.
>
> v3: wording fix-ups and improvements suggested by Kashyap
> v2: add a lot of documentation changes
> v1 was "[PATCH] qapi: deprecate drive-backup"
>
>
> Note, that this series lack deprecating drive-backup transaction action.
> That's done by Markus in 05 patch of
> "[PATCH v4 0/5] qapi: Add feature flags to enum members"
> So, the most effective would be to take these series together.

Works for me.  To make it easier for the maintainer who merges this,
I'll respin this series so it includes my patch.

Thanks!



      parent reply	other threads:[~2021-11-04  5:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-03 13:29 [PATCH v3 0/3] qapi & doc: deprecate drive-backup Vladimir Sementsov-Ogievskiy
2021-11-03 13:29 ` [PATCH v3 1/3] docs/block-replication: use blockdev-backup Vladimir Sementsov-Ogievskiy
2021-11-03 13:29 ` [PATCH v3 2/3] docs/interop/bitmaps: " Vladimir Sementsov-Ogievskiy
2021-11-03 13:29 ` [PATCH v3 3/3] qapi: deprecate drive-backup Vladimir Sementsov-Ogievskiy
2021-11-04 19:38   ` Eric Blake
2021-11-04  5:54 ` Markus Armbruster [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=87a6ikh3dp.fsf@dusky.pond.sub.org \
    --to=armbru@redhat.com \
    --cc=eblake@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=kchamart@redhat.com \
    --cc=libvir-list@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=vsementsov@virtuozzo.com \
    --cc=wencongyang2@huawei.com \
    --cc=xiechanglong.d@gmail.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 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.