From: Eric Blake <eblake@redhat.com>
To: John Snow <jsnow@redhat.com>, Stefan Weil <sw@weilnetz.de>,
QEMU Developer <qemu-devel@nongnu.org>
Cc: Kevin Wolf <kwolf@redhat.com>,
QEMU Trivial <qemu-trivial@nongnu.org>,
qemu-block@nongnu.org, Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-trivial] [Qemu-devel] [Qemu-block] [PATCH] block: Fix typos in comments (found by codespell)
Date: Fri, 20 Jul 2018 16:14:17 -0500 [thread overview]
Message-ID: <e932a87f-83b7-dcc8-d2da-33cc68fa47de@redhat.com> (raw)
In-Reply-To: <07226662-e636-2ff7-5cb4-7a64c6020c04@redhat.com>
On 07/12/2018 03:32 PM, John Snow wrote:
>> +++ b/block/gluster.c
>> @@ -1326,7 +1326,7 @@ static int qemu_gluster_has_zero_init(BlockDriverState *bs)
>> * If @start is in a trailing hole or beyond EOF, return -ENXIO.
>> * If we can't find out, return a negative errno other than -ENXIO.
>> *
>> - * (Shamefully copied from file-posix.c, only miniscule adaptions.)
>> + * (Shamefully copied from file-posix.c, only minuscule adaptions.)
>
> Huh!
>
> Merriam-Webster lists miniscule as a "disputed" spelling of minuscule.
> Dictionary.com simply lists it as an acceptable alternative.
>
> Anyway, this is a change from something dubiously correct to something
> unambiguously correct, so it's fine.
While at it, I would s/adaptions/adaptations/
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2018-07-20 21:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-12 19:51 [Qemu-trivial] [PATCH] block: Fix typos in comments (found by codespell) Stefan Weil
2018-07-12 20:32 ` [Qemu-trivial] [Qemu-block] " John Snow
2018-07-20 21:14 ` Eric Blake [this message]
2018-07-12 20:39 ` [Qemu-trivial] " Jeff Cody
2018-07-13 8:03 ` Kevin Wolf
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=e932a87f-83b7-dcc8-d2da-33cc68fa47de@redhat.com \
--to=eblake@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=sw@weilnetz.de \
/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).