From: Christophe Fergeau <cfergeau@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 1/2] Add \n to the end of fatal spice error messages
Date: Fri, 24 Feb 2012 11:37:53 +0100 [thread overview]
Message-ID: <1330079874-5818-1-git-send-email-cfergeau@redhat.com> (raw)
Without it the shell prompt doesn't appear on a new line after
qemu dies.
---
ui/spice-core.c | 8 ++++----
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/ui/spice-core.c b/ui/spice-core.c
index 1308a3d..6d240a3 100644
--- a/ui/spice-core.c
+++ b/ui/spice-core.c
@@ -568,15 +568,15 @@ void qemu_spice_init(void)
port = qemu_opt_get_number(opts, "port", 0);
tls_port = qemu_opt_get_number(opts, "tls-port", 0);
if (!port && !tls_port) {
- fprintf(stderr, "neither port nor tls-port specified for spice.");
+ fprintf(stderr, "neither port nor tls-port specified for spice.\n");
exit(1);
}
if (port < 0 || port > 65535) {
- fprintf(stderr, "spice port is out of range");
+ fprintf(stderr, "spice port is out of range\n");
exit(1);
}
if (tls_port < 0 || tls_port > 65535) {
- fprintf(stderr, "spice tls-port is out of range");
+ fprintf(stderr, "spice tls-port is out of range\n");
exit(1);
}
password = qemu_opt_get(opts, "password");
@@ -700,7 +700,7 @@ void qemu_spice_init(void)
qemu_opt_foreach(opts, add_channel, NULL, 0);
if (0 != spice_server_init(spice_server, &core_interface)) {
- fprintf(stderr, "failed to initialize spice server");
+ fprintf(stderr, "failed to initialize spice server\n");
exit(1);
};
using_spice = 1;
--
1.7.7.6
next reply other threads:[~2012-02-24 10:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 10:37 Christophe Fergeau [this message]
2012-02-24 10:37 ` [Qemu-devel] [PATCH 2/2] Error out when tls-channel option is used without TLS Christophe Fergeau
2012-02-24 16:49 ` Gerd Hoffmann
2012-02-24 16:47 ` [Qemu-devel] [PATCH 1/2] Add \n to the end of fatal spice error messages 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=1330079874-5818-1-git-send-email-cfergeau@redhat.com \
--to=cfergeau@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).