qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] [RFC] Syncing documentation vs. -help vs. qemu_options table v2
Date: Mon, 16 Mar 2009 14:38:39 -0500	[thread overview]
Message-ID: <49BEAABF.6050908@codemonkey.ws> (raw)
In-Reply-To: <f43fc5580903161223y2415f81cq5d4ec769ccc1396c@mail.gmail.com>

Blue Swirl wrote:
> Hi,
>
> I converted all options to the new system. Because of problems with #
> and ' characters, I had to move from CPP to a Perl scripts. I'm sure
> any Perl expert worth their salt could compress the scripts much
> further. A comment token (HXCOMM?, deleted while parsing) would be
> nice, then there could be comments that describe the syntax and usage
> on top of options.hx.
>
> Comments? Objections?
>   

Adding a perl dependency is really painful for win32.  We could check in 
the resulting options.h but if we can find a way to do it with CPP, that 
would be much better.

Long term, I think there are better ways to generate the man page.  For 
instance, if we had a verbose help setting, we could make use of 
help2man.  But I think this is a step in the right direction (provided 
we can drop the perl dependency).

Regards,

Anthony Liguori

> A related idea: maybe the machine definition files should also enclose
> a mandatory TEXI description, leading to a generated list of machines
> and their devices for qemu-doc.texi.

  reply	other threads:[~2009-03-16 19:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-16 19:23 [Qemu-devel] [PATCH] [RFC] Syncing documentation vs. -help vs. qemu_options table v2 Blue Swirl
2009-03-16 19:38 ` Anthony Liguori [this message]
2009-03-17  9:57 ` Avi Kivity

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=49BEAABF.6050908@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --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).