qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: Eric Blake <eblake@redhat.com>, Michael Tokarev <mjt@tls.msk.ru>,
	qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qemu-options: trivial spelling fix (messsage)
Date: Mon, 27 Apr 2015 12:31:01 -0400	[thread overview]
Message-ID: <553E6445.20309@redhat.com> (raw)
In-Reply-To: <553E4C5C.7010705@redhat.com>



On 04/27/2015 10:49 AM, Eric Blake wrote:
> On 04/27/2015 02:13 AM, Michael Tokarev wrote:
>> Signed-off-by: Michael Tokarev <mjt@tls.msk.ru>
>> ---
>>   qemu-options.hx | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> Reviewed-by: Eric Blake <eblake@redhat.com>
>
> But while at it...
>
>>
>> diff --git a/qemu-options.hx b/qemu-options.hx
>> index 319d971..ec356f6 100644
>> --- a/qemu-options.hx
>> +++ b/qemu-options.hx
>> @@ -3106,7 +3106,7 @@ executed often has little or no correlation with actual performance.
>>   to synchronise the host clock and the virtual clock. The goal is to
>
> Is there any consensus on whether we should prefer US spelling
> (synchronize) over UK spelling in our user-facing text?
>

I would just go with whatever the prevailing standard currently is.

Can we run a spellchecker over our code in a UK mode and then again in a 
US mode, and we'll just go with whatever has the least errors currently?

--js

      reply	other threads:[~2015-04-27 16:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-27  8:13 [Qemu-devel] [PATCH] qemu-options: trivial spelling fix (messsage) Michael Tokarev
2015-04-27 14:49 ` Eric Blake
2015-04-27 16:31   ` John Snow [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=553E6445.20309@redhat.com \
    --to=jsnow@redhat.com \
    --cc=eblake@redhat.com \
    --cc=mjt@tls.msk.ru \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@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).