From: Anthony Liguori <anthony@codemonkey.ws>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PULL 0/3]: QMP queue
Date: Mon, 12 Mar 2012 21:22:28 -0500 [thread overview]
Message-ID: <4F5EAF64.6000503@codemonkey.ws> (raw)
In-Reply-To: <1331326519-12444-1-git-send-email-lcapitulino@redhat.com>
On 03/09/2012 02:55 PM, Luiz Capitulino wrote:
> A few small fixes from Alon.
>
> The changes (since dac6b1b22cbad29ca34735a1e56c9feb9586e3c0) are available
> in the following repository:
>
> git://repo.or.cz/qemu/qmp-unstable.git queue/qmp
>
> Alon Levy (3):
> qjson.h: include compiler.h for GCC_FMT_ATTR
> qapi-schema: fix typos and explain 'spice' auth
> qapi-schema.json: fix comment for type ObjectPropretyInfo
Pulled. Thanks.
Regards,
Anthony Liguori
>
> qapi-schema.json | 16 +++++++++-------
> qjson.h | 1 +
> 2 files changed, 10 insertions(+), 7 deletions(-)
>
>
>
next prev parent reply other threads:[~2012-03-13 2:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-09 20:55 [Qemu-devel] [PULL 0/3]: QMP queue Luiz Capitulino
2012-03-09 20:55 ` [Qemu-devel] [PATCH 1/3] qjson.h: include compiler.h for GCC_FMT_ATTR Luiz Capitulino
2012-03-09 20:55 ` [Qemu-devel] [PATCH 2/3] qapi-schema: fix typos and explain 'spice' auth Luiz Capitulino
2012-03-09 20:55 ` [Qemu-devel] [PATCH 3/3] qapi-schema.json: fix comment for type ObjectPropretyInfo Luiz Capitulino
2012-03-13 2:22 ` Anthony Liguori [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-07-13 16:53 [Qemu-devel] [PULL 0/3]: QMP queue Luiz Capitulino
2012-10-24 13:34 [Qemu-devel] [PULL 0/3] " Luiz Capitulino
2012-10-29 14:35 ` Aurelien Jarno
2013-04-12 13:58 Luiz Capitulino
2013-05-31 14:18 Luiz Capitulino
2013-06-17 21:18 ` Anthony Liguori
2013-06-07 19:54 Luiz Capitulino
2013-06-07 21:02 ` Luiz Capitulino
2014-05-22 13:53 Luiz Capitulino
2014-05-23 10:31 ` Peter Maydell
2014-08-18 19:26 Luiz Capitulino
2014-08-19 11:12 ` Peter Maydell
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=4F5EAF64.6000503@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=lcapitulino@redhat.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).