From: Eric Blake <eblake@redhat.com>
To: Luiz Capitulino <lcapitulino@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: Michal Privoznik <mprivozn@redhat.com>,
famz@redhat.com, qemu-devel@nongnu.org,
Wenchao Xia <wenchaoqemu@gmail.com>
Subject: Re: [Qemu-devel] [PATCH] qmp: add qmp-events.txt back
Date: Thu, 26 Jun 2014 10:31:11 -0600 [thread overview]
Message-ID: <53AC4ACF.3070304@redhat.com> (raw)
In-Reply-To: <20140626094307.6e0c2751@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1580 bytes --]
On 06/26/2014 07:43 AM, Luiz Capitulino wrote:
> Fair enough. Here goes the patch. As each commit dropped a section of the
> file, it was easier just to re-add it. ACKs wanted.
>
> Subject: [PATCH] qmp: add qmp-events.txt back
>
> The conversion of events to the QAPI, resulted in the removal of the
> docs/qmp/qmp-events.txt file. This was done to avoid having duplicated
> information between qmp-events.txt and qapi-event.json.
>
> However, qmp-events.txt contains examples and we're still not sure
> how to proper install QAPI docs in the host. To avoid harming users,
> it's better to re-add qmp-events.txt for now and deal with the
> duplication later.
We'll need some followup patches to fix typos, missing events, and such
to be in parallel with the schema; but a straight revive of the file to
the pre-conversion state is the easiest starting point for those followups.
>
> Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
> ---
> docs/qmp/qmp-events.txt | 551 ++++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 551 insertions(+)
> create mode 100644 docs/qmp/qmp-events.txt
>
> diff --git a/docs/qmp/qmp-events.txt b/docs/qmp/qmp-events.txt
> new file mode 100644
> index 0000000..22fea58
I'm happy that this is a straight revive, based on the output of
git ls-tree 506f40ff:docs/qmp/
git show 506f40ff # patch 1 of the conversion series
Reviewed-by: Eric Blake <eblake@redhat.com>
--
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-06-26 16:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-25 9:30 [Qemu-devel] [PATCH] Makefile: Install qmp-events.txt Michal Privoznik
2014-06-25 9:34 ` Paolo Bonzini
2014-06-25 9:37 ` Michal Privoznik
2014-06-25 13:56 ` Eric Blake
2014-06-25 17:21 ` Markus Armbruster
2014-06-25 19:50 ` Luiz Capitulino
2014-06-25 20:13 ` Eric Blake
2014-06-26 12:46 ` Luiz Capitulino
2014-06-26 13:01 ` Paolo Bonzini
2014-06-26 13:11 ` Eric Blake
2014-06-26 13:14 ` Paolo Bonzini
2014-06-26 13:17 ` Luiz Capitulino
2014-06-26 13:25 ` Paolo Bonzini
2014-06-26 13:43 ` [Qemu-devel] [PATCH] qmp: add qmp-events.txt back Luiz Capitulino
2014-06-26 13:56 ` Paolo Bonzini
2014-06-26 16:31 ` Eric Blake [this message]
2014-06-26 16:25 ` [Qemu-devel] [PATCH] Makefile: Install qmp-events.txt Eric Blake
2014-06-26 16:27 ` Paolo Bonzini
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=53AC4ACF.3070304@redhat.com \
--to=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=mprivozn@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wenchaoqemu@gmail.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).