From: Eric Blake <eblake@redhat.com>
To: peter@gridcentric.ca, qemu-devel@nongnu.org
Cc: lcapitulino@redhat.com
Subject: Re: [Qemu-devel] [PATCH] doc: add "setup" to list of migration states
Date: Fri, 16 May 2014 09:04:28 -0600 [thread overview]
Message-ID: <537628FC.3070506@redhat.com> (raw)
In-Reply-To: <1400251247-11218-1-git-send-email-peter@gridcentric.ca>
[-- Attachment #1: Type: text/plain, Size: 1249 bytes --]
On 05/16/2014 08:40 AM, peter@gridcentric.ca wrote:
> From: Peter Feiner <peter@gridcentric.ca>
>
> On a slow VM (e.g., nested), you see the "setup" state when you query the
> migration status.
>
> Signed-off-by: Peter Feiner <peter@gridcentric.ca>
> ---
> qapi-schema.json | 2 +-
> qmp-commands.hx | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
Reviewed-by: Eric Blake <eblake@redhat.com>
>
> diff --git a/qapi-schema.json b/qapi-schema.json
> index 36cb964..f4ffede 100644
> --- a/qapi-schema.json
> +++ b/qapi-schema.json
> @@ -691,7 +691,7 @@
> # Information about current migration process.
> #
> # @status: #optional string describing the current migration status.
> -# As of 0.14.0 this can be 'active', 'completed', 'failed' or
> +# As of 0.14.0 this can be 'setup', 'active', 'completed', 'failed' or
You know, it would be even nicer to convert from an open-coded 'str' to
a finite enum of valid strings; it would be self-documenting, and make
it that much easier to guarantee the code doesn't add new states without
documenting when they were added.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2014-05-16 15:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 14:40 [Qemu-devel] [PATCH] doc: add "setup" to list of migration states peter
2014-05-16 15:04 ` Eric Blake [this message]
2014-05-20 18:32 ` Luiz Capitulino
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=537628FC.3070506@redhat.com \
--to=eblake@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=peter@gridcentric.ca \
--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).