From: Luiz Capitulino <lcapitulino@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Nathan Baum <nathan@parenthephobia.org.uk>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 11/11] Change the monitor to use the new do_info_qtree.
Date: Tue, 12 Jan 2010 09:24:08 -0200 [thread overview]
Message-ID: <20100112092408.0745d345@doriath> (raw)
In-Reply-To: <m3hbqr7mse.fsf@blackfin.pond.sub.org>
On Tue, 12 Jan 2010 09:25:05 +0100
Markus Armbruster <armbru@redhat.com> wrote:
> > We were considering something along these lines
> > but we didn't consider having the description as part of the dict,
> > for example.
>
> We did, actually :)
That's good then!
> > This solves some issues we were trying to address.
> >
> > The only problem I can see is that the documentation and code will
> > be in different places, which makes it easier to get outdated.
>
> Not necessarily. Documentation will be in whatever place we put it.
> Some places require tools to extract it.
I was thinking in having them on separate file just to make the
work as easy as possible, having a tool to extract them from the
function's documentation is perfect, but I'm afraid you'll have
to come up with your own tags to distinguish among responses,
events, commands etc.
next prev parent reply other threads:[~2010-01-12 11:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1261862362-2530-1-git-send-email-nathan@parenthephobia.org.uk>
[not found] ` <1261862362-2530-12-git-send-email-nathan@parenthephobia.org.uk>
[not found] ` <20091229151508.35c4bc55@doriath>
[not found] ` <1262114724.4088.17.camel@athens>
[not found] ` <20091229191317.6385ae2d@doriath>
2010-01-12 8:25 ` [Qemu-devel] [PATCH 11/11] Change the monitor to use the new do_info_qtree Markus Armbruster
2010-01-12 11:24 ` Luiz Capitulino [this message]
2010-01-12 18:57 ` Making QMP self-documenting (was: [Qemu-devel] [PATCH 11/11] Change the monitor to use the new do_info_qtree.) Markus Armbruster
2010-01-13 12:40 ` 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=20100112092408.0745d345@doriath \
--to=lcapitulino@redhat.com \
--cc=armbru@redhat.com \
--cc=nathan@parenthephobia.org.uk \
--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).