From: Gerd Hoffmann <kraxel@redhat.com>
To: Christophe Fergeau <cfergeau@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCHv2 1/2] spice: use error_report to report errors
Date: Fri, 24 Feb 2012 18:19:21 +0100 [thread overview]
Message-ID: <4F47C699.60805@redhat.com> (raw)
In-Reply-To: <1330103593-11826-1-git-send-email-cfergeau@redhat.com>
On 02/24/12 18:13, Christophe Fergeau wrote:
> Error message reporting during spice startup wasn't consistent, it was done
> with fprintf(stderr, "") but sometimes the message didn't have a trailing
> \n. Using error_report make the intent of the message clearer and deal
> with the final \n for us.
Patch added to spice patch queue.
thanks,
Gerd
prev parent reply other threads:[~2012-02-24 17:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 17:13 [Qemu-devel] [PATCHv2 1/2] spice: use error_report to report errors Christophe Fergeau
2012-02-24 17:13 ` [Qemu-devel] [PATCHv2 2/2] Error out when tls-channel option is used without TLS Christophe Fergeau
2012-02-24 17:20 ` Gerd Hoffmann
2012-02-24 17:28 ` [Qemu-devel] [PATCHv3] " Christophe Fergeau
2012-02-24 17:32 ` Gerd Hoffmann
2012-02-24 17:19 ` Gerd Hoffmann [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=4F47C699.60805@redhat.com \
--to=kraxel@redhat.com \
--cc=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).