From: Markus Armbruster <armbru@redhat.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
Cc: kwolf@redhat.com, pkrempa@redhat.com, berrange@redhat.com,
libvir-list@redhat.com, eblake@redhat.com,
mdroth@linux.vnet.ibm.com, qemu-devel@nongnu.org,
marcandre.lureau@redhat.com, jsnow@redhat.com,
libguestfs@redhat.com
Subject: Re: [PATCH v4 5/5] block: Deprecate transaction type drive-backup
Date: Thu, 04 Nov 2021 06:49:37 +0100 [thread overview]
Message-ID: <87ee7wh3m6.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <c505d2d8-955d-7c64-b769-80ed40428ed5@virtuozzo.com> (Vladimir Sementsov-Ogievskiy's message of "Wed, 3 Nov 2021 16:40:00 +0300")
Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com> writes:
> 25.10.2021 07:24, Markus Armbruster wrote:
>> Several moons ago, Vladimir posted
>>
>> Subject: [PATCH v2 3/3] qapi: deprecate drive-backup
>> Date: Wed, 5 May 2021 16:58:03 +0300
>> Message-Id:<20210505135803.67896-4-vsementsov@virtuozzo.com>
>> https://lists.gnu.org/archive/html/qemu-devel/2021-05/msg01394.html
>>
>> with this
>>
>> TODO: We also need to deprecate drive-backup transaction action..
>> But union members in QAPI doesn't support 'deprecated' feature. I tried
>> to dig a bit, but failed :/ Markus, could you please help with it? At
>> least by advice?
>>
>> This is one way to resolve it. Sorry it took so long.
>>
>> John explored another way, namely adding feature flags to union
>> branches. Could also be useful, say to add different features to
>> branches in multiple unions sharing the same tag enum.
>>
>> Signed-off-by: Markus Armbruster<armbru@redhat.com>
>
> Reviewed-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
>
> (with simplified commit message of course :)
Your "[PATCH v2 0/3] qapi & doc: deprecate drive-backup" series contains
docs/block-replication: use blockdev-backup
docs/interop/bitmaps: use blockdev-backup
qapi: deprecate drive-backup
I figure proper deprecation needs all that, i.e. we need to merge my RFC
patch into your 3/3. Could you take care of that?
next prev parent reply other threads:[~2021-11-04 5:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-25 4:24 [PATCH v4 0/5] qapi: Add feature flags to enum members Markus Armbruster
2021-10-25 4:24 ` [PATCH v4 1/5] qapi: Enable enum member introspection to show more than name Markus Armbruster
2021-10-26 20:44 ` John Snow
2021-10-25 4:24 ` [PATCH v4 2/5] qapi: Add feature flags to enum members Markus Armbruster
2021-10-26 20:48 ` John Snow
2021-10-25 4:24 ` [PATCH v4 3/5] qapi: Move compat policy from QObject to generic visitor Markus Armbruster
2021-10-26 20:50 ` John Snow
2021-10-25 4:24 ` [PATCH v4 4/5] qapi: Implement deprecated-input={reject, crash} for enum values Markus Armbruster
2021-10-25 4:24 ` [PATCH v4 5/5] block: Deprecate transaction type drive-backup Markus Armbruster
2021-10-25 4:34 ` Markus Armbruster
2021-10-26 20:54 ` John Snow
2021-10-27 5:22 ` Markus Armbruster
2021-11-03 13:38 ` Vladimir Sementsov-Ogievskiy
2021-11-03 13:40 ` Vladimir Sementsov-Ogievskiy
2021-11-04 5:49 ` Markus Armbruster [this message]
2021-11-09 17:11 ` 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=87ee7wh3m6.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=libguestfs@redhat.com \
--cc=libvir-list@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=pkrempa@redhat.com \
--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 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.