From: "Hervé Poussineau" <hpoussin@reactos.org>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH] Be consistent in -clock parameter
Date: Thu, 31 Jan 2008 17:14:06 +0100 [thread overview]
Message-ID: <47A1F3CE.4020107@reactos.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 245 bytes --]
Hi,
-soundhw, -M, -cpu, -d, -translation options use the '?' to display the
list of possibilities, whereas -clock uses 'help'. Change it to be
consistent.
Display also the list of available sources if no valid clock name has
been specified.
[-- Attachment #2: clock.diff --]
[-- Type: text/plain, Size: 1337 bytes --]
Index: vl.c
===================================================================
RCS file: /sources/qemu/qemu/vl.c,v
retrieving revision 1.401
diff -u -r1.401 vl.c
--- vl.c 23 Jan 2008 19:01:12 -0000 1.401
+++ vl.c 31 Jan 2008 16:11:12 -0000
@@ -917,7 +917,7 @@
char *arg;
char *name;
- if (!strcmp(opt, "help")) {
+ if (!strcmp(opt, "?")) {
show_available_alarms();
exit(0);
}
@@ -956,13 +956,13 @@
free(arg);
if (cur) {
- /* Disable remaining timers */
+ /* Disable remaining timers */
for (i = cur; i < count; i++)
alarm_timers[i].name = NULL;
+ } else {
+ show_available_alarms();
+ exit(1);
}
-
- /* debug */
- show_available_alarms();
}
QEMUClock *rt_clock;
@@ -7662,7 +7662,7 @@
"-prom-env variable=value set OpenBIOS nvram variables\n"
#endif
"-clock force the use of the given methods for timer alarm.\n"
- " To see what timers are available use -clock help\n"
+ " To see what timers are available use -clock ?\n"
"-startdate select initial date of the Qemu clock\n"
"-translation setting1,... configures code translation\n"
" (use -translation ? for a list of settings)\n"
reply other threads:[~2008-01-31 16:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=47A1F3CE.4020107@reactos.org \
--to=hpoussin@reactos.org \
--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.