From: Amos Kong <akong@redhat.com>
To: qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, aliguori@us.ibm.com, lilei@linux.vnet.ibm.com
Subject: [Qemu-devel] [PATCH] qapi: lack of two commas in dict
Date: Wed, 19 Jun 2013 17:23:28 +0800 [thread overview]
Message-ID: <1371633808-4362-2-git-send-email-akong@redhat.com> (raw)
In-Reply-To: <1371633808-4362-1-git-send-email-akong@redhat.com>
Signed-off-by: Amos Kong <akong@redhat.com>
---
qapi-schema.json | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/qapi-schema.json b/qapi-schema.json
index 128cc58..38acd25 100644
--- a/qapi-schema.json
+++ b/qapi-schema.json
@@ -388,7 +388,7 @@
#
# Since: 1.4
##
-{ 'enum': 'DataFormat'
+{ 'enum': 'DataFormat',
'data': [ 'utf8', 'base64' ] }
##
@@ -1589,7 +1589,7 @@
#
# Since: 1.1
##
-{ 'enum': 'NewImageMode'
+{ 'enum': 'NewImageMode',
'data': [ 'existing', 'absolute-paths' ] }
##
--
1.8.1.4
next prev parent reply other threads:[~2013-06-19 9:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 9:23 [Qemu-devel] [PATCH] qapi: lack of two commas in dict Amos Kong
2013-06-19 9:23 ` Amos Kong [this message]
2013-06-19 13:22 ` [Qemu-devel] [Qemu-trivial] " Michael Tokarev
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=1371633808-4362-2-git-send-email-akong@redhat.com \
--to=akong@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=lilei@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@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).