From: Jan Kiszka <jan.kiszka@web.de>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: [PATCH, RFC] Use hxtool to generate monitor documentation and C structures
Date: Sun, 14 Jun 2009 16:11:43 +0200 [thread overview]
Message-ID: <4A35051F.4070400@web.de> (raw)
In-Reply-To: <f43fc5580905111315v71abf42eo75b2b09fac3dccf1@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 235 bytes --]
Blue Swirl wrote:
> Hi,
>
> The benefit from using a common file is not so great as with
> qemu-options. Comments?
>
What happened to this patch? I would offer to rebase and test it if you
are willing to apply it.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next prev parent reply other threads:[~2009-06-14 14:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-11 20:15 [Qemu-devel] [PATCH, RFC] Use hxtool to generate monitor documentation and C structures Blue Swirl
2009-05-12 8:19 ` [Qemu-devel] " Jan Kiszka
2009-06-14 14:11 ` Jan Kiszka [this message]
2009-06-14 14:14 ` Jan Kiszka
2009-06-14 14:18 ` Blue Swirl
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=4A35051F.4070400@web.de \
--to=jan.kiszka@web.de \
--cc=blauwirbel@gmail.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).