From: Luiz Capitulino <lcapitulino@redhat.com>
To: qemu-devel@nongnu.org
Cc: aliguori@us.ibm.com
Subject: [Qemu-devel] [PULL 0/3] QMP queue
Date: Fri, 12 Apr 2013 09:58:20 -0400 [thread overview]
Message-ID: <1365775103-18737-1-git-send-email-lcapitulino@redhat.com> (raw)
The changes (since 93b48c201eb6c0404d15550a0eaa3c0f7937e35e) are available
in the following repository:
git://repo.or.cz/qemu/qmp-unstable.git queue/qmp
Eric Blake (1):
qapi: use valid JSON in schema
Michal Novotny (2):
New cpu-max field in query-machines QMP command output
Revert "New QMP command query-cpu-max and HMP command cpu_max"
hmp-commands.hx | 2 --
hmp.c | 8 --------
hmp.h | 1 -
monitor.c | 7 -------
qapi-schema.json | 18 +++++-------------
qmp-commands.hx | 22 ----------------------
vl.c | 6 +-----
7 files changed, 6 insertions(+), 58 deletions(-)
--
1.8.1.4
next reply other threads:[~2013-04-12 13:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 13:58 Luiz Capitulino [this message]
2013-04-12 13:58 ` [Qemu-devel] [PULL 1/3] New cpu-max field in query-machines QMP command output Luiz Capitulino
2013-04-12 13:58 ` [Qemu-devel] [PULL 2/3] Revert "New QMP command query-cpu-max and HMP command cpu_max" Luiz Capitulino
2013-04-12 13:58 ` [Qemu-devel] [PULL 3/3] qapi: use valid JSON in schema Luiz Capitulino
-- strict thread matches above, loose matches on Subject: below --
2014-08-18 19:26 [Qemu-devel] [PULL 0/3] QMP queue Luiz Capitulino
2014-08-19 11:12 ` Peter Maydell
2014-05-22 13:53 Luiz Capitulino
2014-05-23 10:31 ` Peter Maydell
2013-06-07 19:54 Luiz Capitulino
2013-06-07 21:02 ` Luiz Capitulino
2013-05-31 14:18 Luiz Capitulino
2013-06-17 21:18 ` Anthony Liguori
2012-10-24 13:34 Luiz Capitulino
2012-10-29 14:35 ` Aurelien Jarno
2012-07-13 16:53 [Qemu-devel] [PULL 0/3]: " Luiz Capitulino
2012-03-09 20:55 Luiz Capitulino
2012-03-13 2:22 ` Anthony Liguori
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=1365775103-18737-1-git-send-email-lcapitulino@redhat.com \
--to=lcapitulino@redhat.com \
--cc=aliguori@us.ibm.com \
--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).