From: Markus Armbruster <armbru@redhat.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: aliguori@us.ibm.com, qemu-devel@nongnu.org, avi@redhat.com
Subject: Re: [Qemu-devel] [PATCH 3/3] Monitor: Drop QMP documentation from code
Date: Fri, 21 May 2010 08:37:29 +0200 [thread overview]
Message-ID: <m3mxvtu5ee.fsf@blackfin.pond.sub.org> (raw)
In-Reply-To: <1274232769-11160-4-git-send-email-lcapitulino@redhat.com> (Luiz Capitulino's message of "Tue, 18 May 2010 22:32:49 -0300")
Luiz Capitulino <lcapitulino@redhat.com> writes:
> Previous commit added the QMP/qmp-commands.txt file, which is a
> copy of this information.
This is no longer true.
> While it's good to keep it near code, maintaining two copies of
> the same information is too hard and has little benefit as we
> don't expect client writers to consult the code to find how to
> use a QMP command.
>
> Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
[...]
next prev parent reply other threads:[~2010-05-21 6:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-19 1:32 [Qemu-devel] [PATCH v3 0/3]: QMP: Commands doc Luiz Capitulino
2010-05-19 1:32 ` [Qemu-devel] [PATCH 1/3] monitor: Reorder info documentation Luiz Capitulino
2010-05-19 1:32 ` [Qemu-devel] [PATCH 2/3] QMP: Introduce commands documentation Luiz Capitulino
2010-05-19 9:15 ` [Qemu-devel] " Jan Kiszka
2010-05-19 13:06 ` Luiz Capitulino
2010-05-19 13:30 ` Jan Kiszka
2010-05-19 13:46 ` Luiz Capitulino
2010-05-19 13:50 ` Jan Kiszka
2010-05-19 13:55 ` Luiz Capitulino
2010-05-19 1:32 ` [Qemu-devel] [PATCH 3/3] Monitor: Drop QMP documentation from code Luiz Capitulino
2010-05-21 6:37 ` Markus Armbruster [this message]
2010-05-29 8:50 ` [Qemu-devel] Re: [PATCH v3 0/3]: QMP: Commands doc Jan Kiszka
2010-05-31 13:52 ` Luiz Capitulino
-- strict thread matches above, loose matches on Subject: below --
2010-05-31 17:43 [Qemu-devel] [PATCH v4 " Luiz Capitulino
2010-05-31 17:43 ` [Qemu-devel] [PATCH 3/3] 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=m3mxvtu5ee.fsf@blackfin.pond.sub.org \
--to=armbru@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=avi@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.