From: "Daniel P. Berrange" <berrange@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org, Eric Blake <eblake@redhat.com>,
Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org
Subject: Re: [Qemu-devel] qapi: Stop abusing "special" values for something entirely different
Date: Mon, 17 Jul 2017 10:02:28 +0100 [thread overview]
Message-ID: <20170717090228.GE3640@redhat.com> (raw)
In-Reply-To: <87379zhrhn.fsf@dusky.pond.sub.org>
On Fri, Jul 14, 2017 at 07:12:52PM +0200, Markus Armbruster wrote:
> Here's what I propose to do:
>
> 1. Stop abusing values the schema accepts, but are invalid to mean "do
> something else entirely".
>
> 2. Add a first class null type to QAPI.
>
> 3. Turn MigrationParameters members tls-creds and tls-hostname into
> alternate of str and null. Deprecate "".
>
> 4. Add a null member to alternate BlockdefRef. Deprecate "".
>
> I got patches for 2., and I intend to work on 3. and 4.
>
> Since this is "only" about "less than general and ugly", we may decide
> to leave things as they are if my patches turn out even uglier.
>
> Meanwhile, opinions?
That sounds ok in principle to me, so worth at least proposing the patches
so we can see how it works out in practice.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2017-07-17 9:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-14 17:12 [Qemu-devel] qapi: Stop abusing "special" values for something entirely different Markus Armbruster
2017-07-14 17:38 ` Eric Blake
2017-07-18 15:42 ` Markus Armbruster
2017-07-17 9:02 ` Daniel P. Berrange [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=20170717090228.GE3640@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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).