From: Stefan Weil <weil@mail.berlios.de>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: Anthony Liguori <aliguori@us.ibm.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH RESEND(REBASED)] Fix trivial "endianness bugs"
Date: Fri, 01 Apr 2011 22:51:15 +0200 [thread overview]
Message-ID: <4D963AC3.3010209@mail.berlios.de> (raw)
In-Reply-To: <20110401202725.GC31037@volta.aurel32.net>
Am 01.04.2011 22:27, schrieb Aurelien Jarno:
> On Sun, Mar 13, 2011 at 03:44:02PM +0100, Stefan Weil wrote:
>> Replace endianess -> endianness.
>
> Given it concerns code and not comments, I am reluctant for this kind of
> patches unless we have a very good reason.
>
> Do you have some pointers about "endianness" being the correct wording?
> It seems both are accepted, even if in the last years people seems to
> use more often "endianness" than "endianess".
>
> Maybe a native speaker can help us here.
>
Hello Aurelien,
I'm not a native speaker, but I like having well written examples
which help me avoiding mistakes (some of the wrong spellings
were written by me) and improving my knowledge of English.
Therefore I also modified code.
It was a formal replace operation using perl -pi -e,
so this should be rather safe.
Here are some links (other than google which also refers to
endianness):
http://de.wikipedia.org/wiki/Endianess (Falschschreibung = wrong spelling)
http://fr.wikipedia.org/wiki/Endianess (redirected to Endianness)
http://en.wikipedia.org/wiki/Endianess (redirected to Endianness)
This article uses both variants (which obviously is a bug).
Oxford dictionary (like others) does not know any endianness,
but refers to indianness which is a similar composition of
a word ending with "n" followed by "ness".
Regards,
Stefan
next prev parent reply other threads:[~2011-04-01 20:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-13 14:44 [Qemu-devel] [PATCH RESEND(REBASED)] Fix trivial "endianness bugs" Stefan Weil
2011-04-01 20:27 ` Aurelien Jarno
2011-04-01 20:51 ` Stefan Weil [this message]
2011-04-01 22:52 ` Peter Maydell
2011-04-03 19:46 ` Aurelien Jarno
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=4D963AC3.3010209@mail.berlios.de \
--to=weil@mail.berlios.de \
--cc=aliguori@us.ibm.com \
--cc=aurelien@aurel32.net \
--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 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.