All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: bazulay@redhat.com, juzhang@redhat.com,
	Avi Kivity <avi@redhat.com>,
	qemu-devel@nongnu.org, armbru@redhat.com
Subject: [Qemu-devel] Re: [PATCH 1/2] QMP: Introduce commands doc
Date: Fri, 14 May 2010 18:52:44 +0200	[thread overview]
Message-ID: <4BED7FDC.7030208@siemens.com> (raw)
In-Reply-To: <1273086712-29163-2-git-send-email-lcapitulino@redhat.com>

Luiz Capitulino wrote:
> One of the most important missing feature in QMP today is its
> supported commands documentation.
> 
> The plan is to make it part of self-description support, however
> self-description is a big task we have been postponing for a
> long time now and still don't know when it's going to be done.
> 
> In order not to compromise QMP adoption and make users' life easier,
> this commit adds a simple text documentation which fully describes
> all QMP supported commands.
> 
> This is not ideal for a number of reasons (harder to maintain,
> text-only, etc) but does improve the current situation.

Even if it's temporary - maintaining it in a separate file looks rather
unhandy.

Can't we generate the per-command documentation snippets also from
qemu-monitor.hx and merge them with a header/footer into some text file?
That .hx file is the one anyone adding/converting commands has to touch
anyway.

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

  parent reply	other threads:[~2010-05-14 16:52 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   ` Jan Kiszka [this message]
2010-05-14 17:01     ` [Qemu-devel] " Avi Kivity
2010-05-14 17:02       ` Avi Kivity
2010-05-14 17:08         ` Jan Kiszka
2010-05-14 17:12           ` Avi Kivity
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=4BED7FDC.7030208@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=armbru@redhat.com \
    --cc=avi@redhat.com \
    --cc=bazulay@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.