From: Gerd Hoffmann <kraxel@redhat.com>
To: Matthew Booth <mbooth@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH] Documentation: Add documentation for -chardev
Date: Fri, 30 Oct 2009 10:17:41 +0100 [thread overview]
Message-ID: <4AEAAF35.8080808@redhat.com> (raw)
In-Reply-To: <1256835400-16258-2-git-send-email-mbooth@redhat.com>
On 10/29/09 17:56, Matthew Booth wrote:
> +DEFHEADING()
> +
> +DEFHEADING(Character device options:)
> +
> +DEF("chardev", HAS_ARG, QEMU_OPTION_chardev,
> + "-chardev null[,id=id]\n"
> + " A void device. This device will not emit any data, and will\n"
> + " drop any data it receives.\n"
I'd try to keep this shorter to not bloat the -help text. Just list the
options, like this:
-chardev null,id=id
-chardev socket,id=id,path=path[,...] (unix)
-chardev socket,id=id,port=port[,...] (tcp)
-chardev udp,...
maybe? The detailed descriptions are in the man-page.
Oh, and id is *not* optional (would be pointless as you would have no
way to use the chardev), so it shouldn't be listed in brackets.
> +STEXI
> +
> +The general form of a character device option is:
> +@table @option
> +
> +@item -chardev @var{backend} [,id=@var{id}] [,@var{options}]
Same here.
> +@item -chardev vc [,id=@var{id}]
> +
> +Connect to a QEMU text console. @option{vc} does not take any options.
It takes options for the scren size: width+height (pixels) or cols+rows
(chars) (see console.c).
Otherwise the patch looks fine.
Thanks for doing this,
Gerd
next prev parent reply other threads:[~2009-10-30 9:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-29 16:03 [Qemu-devel] [PATCH] Documentation: Add documentation for -chardev Matthew Booth
2009-10-29 16:03 ` Matthew Booth
2009-10-29 16:56 ` Matthew Booth
2009-10-29 16:56 ` Matthew Booth
2009-10-30 9:17 ` Gerd Hoffmann [this message]
2009-10-30 10:56 ` [Qemu-devel] " Matthew Booth
2009-10-30 11:04 ` Gerd Hoffmann
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=4AEAAF35.8080808@redhat.com \
--to=kraxel@redhat.com \
--cc=mbooth@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.