qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: "bazulay@redhat.com" <bazulay@redhat.com>,
	"juzhang@redhat.com" <juzhang@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"armbru@redhat.com" <armbru@redhat.com>,
	Luiz Capitulino <lcapitulino@redhat.com>
Subject: [Qemu-devel] Re: [PATCH 1/2] QMP: Introduce commands doc
Date: Fri, 14 May 2010 20:12:32 +0300	[thread overview]
Message-ID: <4BED8480.3030806@redhat.com> (raw)
In-Reply-To: <4BED8377.7040000@siemens.com>

On 05/14/2010 08:08 PM, Jan Kiszka wrote:
>
>> I mean, a patch introducing or modifying a monitor command.
>>      
> The snippets should be readable by themselves.

They may be readable, but that doesn't mean anyone will read them.  It's 
a lot easier for someone who isn't involved in the code (the libvirt 
people, or me) to review standalone documentation than something 
embedded in a patch (typically at the very end).

> I'm only proposing to
> keep them in the central file, at the same location where the others
> are. There is no difference compared to existing monitor commands, we
> just add the third documentation snippet, this time for QMP.
>    

That's fine.  But the fact that a lot of review comments pointing out 
issues surface only now show that we need to make things easier for 
reviewers.  It's much harder to fix an external interface than an 
internal one.

> Distributing a generated QMP/qmp-commands.txt is another thing, maybe a
> useful one.
>    

Sure, like the other qemu documentation.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.

  reply	other threads:[~2010-05-14 17:12 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-05 19:11 [Qemu-devel] [PATCH v2 0/2]: QMP: Commands doc Luiz Capitulino
2010-05-05 19:11 ` [Qemu-devel] [PATCH 1/2] QMP: Introduce commands doc Luiz Capitulino
2010-05-12 16:48   ` Markus Armbruster
2010-05-12 21:17     ` Luiz Capitulino
2010-05-13  7:01       ` Markus Armbruster
2010-05-13 13:15         ` Luiz Capitulino
2010-05-14 11:29       ` Kevin Wolf
2010-05-13 13:48   ` Avi Kivity
2010-05-13 14:55     ` Luiz Capitulino
2010-05-13 15:01       ` Daniel P. Berrange
2010-05-13 16:23         ` Avi Kivity
2010-05-13 21:57           ` Luiz Capitulino
2010-05-14  8:33             ` Markus Armbruster
2010-05-14 16:42               ` Avi Kivity
2010-05-14 17:06                 ` Markus Armbruster
2010-05-13 15:05       ` Avi Kivity
2010-05-14  8:39       ` Markus Armbruster
2010-05-14 15:07         ` Luiz Capitulino
2010-05-14  8:50     ` Markus Armbruster
2010-05-14 15:43       ` Avi Kivity
2010-05-14 17:03         ` Markus Armbruster
2010-05-14 17:09           ` Avi Kivity
2010-05-17  8:27             ` Markus Armbruster
2010-05-17  9:09               ` Avi Kivity
2010-05-17 11:19                 ` Markus Armbruster
2010-05-17 18:01                   ` Anthony Liguori
2010-05-17 19:21                     ` Gerd Hoffmann
2010-05-18  6:55                       ` Avi Kivity
2010-05-14 22:54           ` Luiz Capitulino
2010-05-15  6:19             ` Avi Kivity
2010-05-17  8:27               ` Markus Armbruster
2010-05-17 18:10               ` Anthony Liguori
2010-05-17 18:12                 ` Avi Kivity
2010-05-18  9:51                 ` Markus Armbruster
2010-05-18 12:45                   ` Luiz Capitulino
2010-05-14  8:52     ` Markus Armbruster
2010-05-14 16:52   ` [Qemu-devel] " Jan Kiszka
2010-05-14 17:01     ` Avi Kivity
2010-05-14 17:02       ` Avi Kivity
2010-05-14 17:08         ` Jan Kiszka
2010-05-14 17:12           ` Avi Kivity [this message]
2010-05-14 23:10           ` Luiz Capitulino
2010-05-15  8:42             ` Jan Kiszka
2010-05-17 13:22               ` Luiz Capitulino
2010-05-18 11:21               ` Markus Armbruster
2010-05-18 12:48                 ` Luiz Capitulino
2010-05-05 19:11 ` [Qemu-devel] [PATCH 2/2] Monitor: Drop QMP documentation from code Luiz Capitulino

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=4BED8480.3030806@redhat.com \
    --to=avi@redhat.com \
    --cc=armbru@redhat.com \
    --cc=bazulay@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=juzhang@redhat.com \
    --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).