From: Blue Swirl <blauwirbel@gmail.com>
To: Jan Kiszka <jan.kiszka@web.de>
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 17:18:20 +0300 [thread overview]
Message-ID: <f43fc5580906140718t43fc53a6nd8b164af477b240@mail.gmail.com> (raw)
In-Reply-To: <4A35051F.4070400@web.de>
On 6/14/09, Jan Kiszka <jan.kiszka@web.de> wrote:
> 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.
Applied long time ago:
commit 2313086addaf609c5f64636591818eebc213fd53
Author: Blue Swirl <blauwirbel@gmail.com>
Date: Sat Jun 6 08:22:04 2009 +0000
Use hxtool to generate monitor documentation and C structures
Signed-off-by: Blue Swirl <blauwirbel@gmail.com>
For some reason, I never see my commits on qemu-commits list, unless
they are made by someone else.
prev parent reply other threads:[~2009-06-14 14:18 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
2009-06-14 14:14 ` Jan Kiszka
2009-06-14 14:18 ` Blue Swirl [this message]
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=f43fc5580906140718t43fc53a6nd8b164af477b240@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=jan.kiszka@web.de \
--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).