From: Luiz Capitulino <lcapitulino@redhat.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Seiji Aguchi <seiji.aguchi@hds.com>,
lersek@redhat.com, qemu-devel@nongnu.org,
tomoki.sekiyama@hds.com
Subject: Re: [Qemu-devel] [PATCH] Convert stderr message calling error_get_pretty() to error_report() to prepend timestamp
Date: Mon, 29 Jul 2013 17:45:44 -0400 [thread overview]
Message-ID: <20130729174544.104eecd0@redhat.com> (raw)
In-Reply-To: <51F6DD54.2060503@suse.de>
On Mon, 29 Jul 2013 23:23:32 +0200
Andreas Färber <afaerber@suse.de> wrote:
> Am 29.07.2013 23:20, schrieb Luiz Capitulino:
> > On Mon, 22 Jul 2013 23:23:29 +0200
> > Andreas Färber <afaerber@suse.de> wrote:
> >> Am 22.07.2013 23:03, schrieb Seiji Aguchi:
> >>> Convert stderr messages calling error_get_pretty()
> >>> to error_report().
> >>
> >> How is this related to error_get_pretty()?
> >
> > Yeah, we're converting fprintf(stderr,) calls to error_report() so that
> > error messages get a timestamp.
>
> Want to add that to my http://wiki.qemu.org/DeveloperNews so that people
> reading it stop adding new ones? :)
Big IMHO here, but honestly speaking I'm not a huge fan of error_report()
because I think that random code shouldn't be allowed to print to the
monitor (only HMP code should).
But it's widespread and it's where the timestamp lives, so calling fprintf()
instead of error_report() will probably start hurting soon.
next prev parent reply other threads:[~2013-07-29 21:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 21:03 [Qemu-devel] [PATCH] Convert stderr message calling error_get_pretty() to error_report() to prepend timestamp Seiji Aguchi
2013-07-22 21:23 ` Andreas Färber
2013-07-23 6:47 ` Markus Armbruster
2013-07-29 21:20 ` Luiz Capitulino
2013-07-29 21:23 ` Andreas Färber
2013-07-29 21:45 ` Luiz Capitulino [this message]
2013-07-30 0:00 ` Markus Armbruster
2013-07-30 0:34 ` Luiz Capitulino
2013-07-30 1:22 ` Seiji Aguchi
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=20130729174544.104eecd0@redhat.com \
--to=lcapitulino@redhat.com \
--cc=afaerber@suse.de \
--cc=lersek@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=seiji.aguchi@hds.com \
--cc=tomoki.sekiyama@hds.com \
/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.