From: Laszlo Ersek <lersek@redhat.com>
To: Andrew Jones <drjones@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] vl.c: Replace fprintf(stderr) with error_report()
Date: Wed, 28 Oct 2015 16:27:42 +0100 [thread overview]
Message-ID: <5630E96E.9010407@redhat.com> (raw)
In-Reply-To: <20151028135800.GB5861@hawk.localdomain>
On 10/28/15 14:58, Andrew Jones wrote:
> On Tue, Oct 27, 2015 at 08:36:07PM +0100, Laszlo Ersek wrote:
>> On 10/27/15 20:25, Eduardo Habkost wrote:
>>> On Tue, Oct 27, 2015 at 08:30:38AM +0100, Andrew Jones wrote:
>>>> In addition to Markus' and Eric's comments, I think we should
>>>>
>>>> 1. make sure the first word's case is correct. Lowercase for phrases,
>>>> uppercase for sentences and proper nouns.
>>>
>>> I think I can understand this in the more obvious cases, but I don't
>>> know how I could convert the following instance:
>>>
>>> [...]
>>>>> case QEMU_OPTION_no_kvm_pit: {
>>>>> - fprintf(stderr, "Warning: KVM PIT can no longer be disabled "
>>>>> - "separately.\n");
>>>>> + error_report("Warning: KVM PIT can no longer be disabled "
>>>>> + "separately.");
>>>>
>>>> Could change this from a sentence into a phrase. Also, we need a consistent
>>>> 'warning' prefix. Should we make a error_report_warn variant?
>>>
>>> Converting that sentence to a phrase is beyond my non-native english
>>> speaker skills. Do you have any suggestions? :)
>>>
>>
>> easy-peasy, "KVM PIT no longer disableable separately"!
>>
>> /me hides ;)
> As well you should with a word like "disableable" :-)
>
> How about
>
> Warning: ignoring deprecated option no-kvm-pit
heh, side-stepping the problem semantically; that's a trick I'll steal! :)
>
> drew
>
>>
prev parent reply other threads:[~2015-10-28 15:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 17:13 [Qemu-devel] [PATCH] vl.c: Replace fprintf(stderr) with error_report() Eduardo Habkost
2015-10-26 17:43 ` Markus Armbruster
2015-10-26 18:03 ` Eduardo Habkost
2015-10-26 18:21 ` Eduardo Habkost
2015-10-28 18:12 ` Eduardo Habkost
2015-10-29 6:15 ` Markus Armbruster
2015-10-26 19:10 ` Eric Blake
2015-10-27 17:08 ` Eduardo Habkost
2015-10-27 7:30 ` Andrew Jones
2015-10-27 9:53 ` Markus Armbruster
2015-10-27 19:25 ` Eduardo Habkost
2015-10-27 19:36 ` Laszlo Ersek
2015-10-28 13:58 ` Andrew Jones
2015-10-28 15:27 ` Laszlo Ersek [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=5630E96E.9010407@redhat.com \
--to=lersek@redhat.com \
--cc=armbru@redhat.com \
--cc=drjones@redhat.com \
--cc=ehabkost@redhat.com \
--cc=pbonzini@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).