qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
	Luiz Capitulino <lcapitulino@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] Makefile: Install qmp-events.txt
Date: Thu, 26 Jun 2014 07:11:47 -0600	[thread overview]
Message-ID: <53AC1C13.40308@redhat.com> (raw)
In-Reply-To: <53AC19C3.10502@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1446 bytes --]

On 06/26/2014 07:01 AM, Paolo Bonzini wrote:
> Il 26/06/2014 14:46, Luiz Capitulino ha scritto:
>>> >
>>> > Michal's hack at least ensures that we have event documentation,
>>> even if
>>> > the format changed compared to the 2.0 docs, and even if we don't have
>>> > time to get something better in place before 2.1 goes out.  So all of
>>> > this conversation on ways to do better is nice, but if we don't get
>>> > there quickly, I could at least live with Michal's patch in the
>>> short term.
>> I honestly don't know what's the best thing to do here. I can live with
>> this patch too, although having some introductory comments at the top of
>> the file saying what it is would be nicer.
> 
> Can we just revert to the pre-conversion qmp-events.txt file?  This is
> similar to the situation with qmp-commands.hx.

As in, carrying redundant information between two files?  True that it's
no worse than qmp-commands.hx; it would also ensure we aren't regressing
on quality of user documentation in relation to prior releases.  We
could do the restore of that file, but if we do, we should fix the bugs
in pre-conversion qmp-events.txt (a couple events were undocumented,
there were some grammar errors, all fixed as part of the conversion), as
well as document events that have been added post-conversion.

-- 
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 --]

  reply	other threads:[~2014-06-26 13:12 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 [this message]
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
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=53AC1C13.40308@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).