From: Matthias <matthias.bgg@googlemail.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: matthias.bgg@googlemail.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] block.c typo in comment fixed
Date: Tue, 01 Nov 2011 11:53:16 +0000 [thread overview]
Message-ID: <4EAFDDAC.2090408@gmail.com> (raw)
In-Reply-To: <20111101083905.GB28223@stefanha-thinkpad.localdomain>
On 11/01/2011 08:39 AM, Stefan Hajnoczi wrote:
> On Tue, Nov 01, 2011 at 01:36:42AM +0000, matthias.bgg@googlemail.com wrote:
>> From: Matthias Brugger<matthias.bgg@gmail.com>
>>
>>
>> Signed-off-by: Matthias Brugger<matthias.bgg@gmail.com>
>> ---
>> block.c | 2 +-
>> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> "Writable" is also a common spelling. Try git grep writable and compare
> against git grep writeable. In qemu.git "writable" actually dominates
> by a large majority so we should leave this alone.
>
> Stefan
Alright, I didn't know that. Sorry for the noise.
Regards,
Matthias
--
---
http://motzblog.wordpress.com/
prev parent reply other threads:[~2011-11-01 10:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-01 1:36 [Qemu-devel] [PATCH] block.c typo in comment fixed matthias.bgg
2011-11-01 7:24 ` Stefan Weil
2011-11-01 8:39 ` Stefan Hajnoczi
2011-11-01 11:53 ` Matthias [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=4EAFDDAC.2090408@gmail.com \
--to=matthias.bgg@googlemail.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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.