From: Kevin Wolf <kwolf@redhat.com>
To: qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>
Subject: [Qemu-devel] [PATCH 3/3] Documentation: Move msmouse description to an appropriate place
Date: Fri, 9 Oct 2009 10:58:37 +0200 [thread overview]
Message-ID: <1255078717-5734-4-git-send-email-kwolf@redhat.com> (raw)
In-Reply-To: <1255078717-5734-1-git-send-email-kwolf@redhat.com>
Putting it right in the middle of the explanation for "-serial udp" probably
wasn't the best idea.
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
---
qemu-options.hx | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/qemu-options.hx b/qemu-options.hx
index e86264e..eba9e52 100644
--- a/qemu-options.hx
+++ b/qemu-options.hx
@@ -1251,8 +1251,6 @@ This implements UDP Net Console.
When @var{remote_host} or @var{src_ip} are not specified
they default to @code{0.0.0.0}.
When not using a specified @var{src_port} a random port is automatically chosen.
-@item msmouse
-Three button serial mouse. Configure the guest to use Microsoft protocol.
If you just want a simple readonly console you can use @code{netcat} or
@code{nc}, by starting qemu with: @code{-serial udp::4555} and nc as:
@@ -1326,6 +1324,8 @@ listening on port 4444 would be:
Braille device. This will use BrlAPI to display the braille output on a real
or fake device.
+@item msmouse
+Three button serial mouse. Configure the guest to use Microsoft protocol.
@end table
ETEXI
--
1.6.2.5
prev parent reply other threads:[~2009-10-09 8:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-09 8:58 [Qemu-devel] [PATCH 0/3] Man page improvements Kevin Wolf
2009-10-09 8:58 ` [Qemu-devel] [PATCH 1/3] Documentation: Highlight placeholders in suboptions Kevin Wolf
2009-10-09 8:58 ` [Qemu-devel] [PATCH 2/3] Documentation: Add missing tags to placeholders Kevin Wolf
2009-10-09 8:58 ` Kevin Wolf [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=1255078717-5734-4-git-send-email-kwolf@redhat.com \
--to=kwolf@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 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).