From: Stefan Weil <weil@mail.berlios.de>
To: QEMU Developers <qemu-devel@nongnu.org>
Cc: Stefan Weil <stefan@weilnetz.de>
Subject: [Qemu-devel] [PATCH] Add missing linefeed in error message
Date: Sat, 8 Aug 2009 23:33:26 +0200 [thread overview]
Message-ID: <1249767206-9802-1-git-send-email-weil@mail.berlios.de> (raw)
From: Stefan Weil <stefan@weilnetz.de>
The error message for an unknown network device given to
monitor command set_link looks better with a terminating
linefeed.
Signed-off-by: Stefan Weil <weil@mail.berlios.de>
---
net.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/net.c b/net.c
index b5e8c9f..85f3727 100644
--- a/net.c
+++ b/net.c
@@ -2917,7 +2917,7 @@ int do_set_link(Monitor *mon, const char *name, const char *up_or_down)
done:
if (!vc) {
- monitor_printf(mon, "could not find network device '%s'", name);
+ monitor_printf(mon, "could not find network device '%s'\n", name);
return 0;
}
--
1.5.6.5
reply other threads:[~2009-08-08 21:33 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=1249767206-9802-1-git-send-email-weil@mail.berlios.de \
--to=weil@mail.berlios.de \
--cc=qemu-devel@nongnu.org \
--cc=stefan@weilnetz.de \
/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).