From: Kevin Wolf <kwolf@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: vsementsov@virtuozzo.com, berrange@redhat.com,
qemu-devel@nongnu.org, mdroth@linux.vnet.ibm.com,
Markus Armbruster <armbru@redhat.com>,
libvir-list@redhat.com, pkrempa@redhat.com,
marcandre.lureau@redhat.com, jsnow@redhat.com,
libguestfs@redhat.com
Subject: Re: [PATCH RFC v2 5/5] block: Deprecate transaction type drive-backup
Date: Tue, 12 Oct 2021 12:52:58 +0200 [thread overview]
Message-ID: <YWVpCp1VcsnfYVkF@redhat.com> (raw)
In-Reply-To: <20211011185817.czv4tmlsxiyhuqrp@redhat.com>
Am 11.10.2021 um 20:58 hat Eric Blake geschrieben:
> On Sat, Oct 09, 2021 at 02:09:44PM +0200, 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>
> > ---
> > qapi/transaction.json | 5 ++++-
> > 1 file changed, 4 insertions(+), 1 deletion(-)
> >
> > diff --git a/qapi/transaction.json b/qapi/transaction.json
> > index d175b5f863..0564a893b3 100644
> > --- a/qapi/transaction.json
> > +++ b/qapi/transaction.json
> > @@ -54,6 +54,9 @@
> > # @blockdev-snapshot-sync: since 1.1
> > # @drive-backup: Since 1.6
> > #
> > +# Features:
> > +# @deprecated: Member @drive-backup is deprecated. Use FIXME instead.
>
> Obviously, we'd need to flesh this out ("'blockdev-backup' with proper
> node names"? something else?) before dropping RFC on this patch.
What does 'blockdev-backup' with improper node names look like?
I think it's sufficient to say "Use @blockdev-backup instead", which is
already documented to take a node/device name instead of a file name.
> And we'd want to edit docs/about/deprecated.rst to match.
Yes.
Kevin
next prev parent reply other threads:[~2021-10-12 11:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-09 12:09 [PATCH v2 0/5] qapi: Add feature flags to enum members Markus Armbruster
2021-10-09 12:09 ` [PATCH v2 1/5] qapi: Enable enum member introspection to show more than name Markus Armbruster
2021-10-11 18:37 ` Eric Blake
2021-10-12 10:08 ` Kevin Wolf
2021-10-21 7:45 ` Markus Armbruster
2021-10-09 12:09 ` [PATCH v2 2/5] qapi: Add feature flags to enum members Markus Armbruster
2021-10-12 10:41 ` Kevin Wolf
2021-10-21 8:48 ` Markus Armbruster
2021-10-09 12:09 ` [PATCH v2 3/5] qapi: Move compat policy from QObject to generic visitor Markus Armbruster
2021-10-09 12:09 ` [PATCH v2 4/5] qapi: Implement deprecated-input={reject, crash} for enum values Markus Armbruster
2021-10-11 18:53 ` [PATCH v2 4/5] qapi: Implement deprecated-input={reject,crash} " Eric Blake
2021-10-21 9:40 ` Markus Armbruster
2021-10-09 12:09 ` [PATCH RFC v2 5/5] block: Deprecate transaction type drive-backup Markus Armbruster
2021-10-11 18:58 ` Eric Blake
2021-10-12 10:52 ` Kevin Wolf [this message]
2021-10-21 9:47 ` Markus Armbruster
2021-10-12 12:39 ` [PATCH v2 0/5] qapi: Add feature flags to enum members Peter Krempa
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=YWVpCp1VcsnfYVkF@redhat.com \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=jsnow@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 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).