From: Fam Zheng <famz@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>, qemu-devel@nongnu.org
Cc: Anthony Liguori <aliguori@amazon.com>
Subject: Re: [Qemu-devel] [PATCH] qapi-schema: fix QEMU 1.8 references
Date: Wed, 11 Dec 2013 17:49:21 +0800 [thread overview]
Message-ID: <52A83521.4030202@redhat.com> (raw)
In-Reply-To: <1386751754-5753-1-git-send-email-stefanha@redhat.com>
On 2013年12月11日 16:49, Stefan Hajnoczi wrote:
> We are moving boldly on to QEMU 2.0 in the next release. Some patches
> written at a time where we assumed 1.8 would be the next version number
> managed to sneak in.
>
> s/1.8/2.0/ in qapi-schema.json
>
> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
> ---
> qapi-schema.json | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/qapi-schema.json b/qapi-schema.json
> index d6f8615..5aa4581 100644
> --- a/qapi-schema.json
> +++ b/qapi-schema.json
> @@ -949,7 +949,7 @@
> # (only present if removable is true)
> #
> # @dirty-bitmaps: #optional dirty bitmaps information (only present if the
> -# driver has one or more dirty bitmaps) (Since 1.8)
> +# driver has one or more dirty bitmaps) (Since 2.0)
> #
> # @io-status: #optional @BlockDeviceIoStatus. Only present if the device
> # supports it and the VM is configured to stop on errors
> @@ -3022,7 +3022,7 @@
> #
> # @devname: #optional path of the netmap device (default: '/dev/netmap').
> #
> -# Since 1.8
> +# Since 2.0
> ##
> { 'type': 'NetdevNetmapOptions',
> 'data': {
>
Reviewed-by: Fam Zheng <famz@redhat.com>
next prev parent reply other threads:[~2013-12-11 9:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-11 8:49 [Qemu-devel] [PATCH] qapi-schema: fix QEMU 1.8 references Stefan Hajnoczi
2013-12-11 9:49 ` Fam Zheng [this message]
2013-12-11 17:32 ` Eric Blake
2013-12-17 2:36 ` Fam Zheng
2013-12-16 16:18 ` Stefan Hajnoczi
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=52A83521.4030202@redhat.com \
--to=famz@redhat.com \
--cc=aliguori@amazon.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).