From: Jani Nikula <jani.nikula@linux.intel.com>
To: Will Deacon <will.deacon@arm.com>, linux-doc@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Will Deacon <will.deacon@arm.com>,
David Howells <dhowells@redhat.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Chris Wilson <chris@chris-wilson.co.uk>,
Michael Halcrow <mhalcrow@google.com>,
Jonathan Corbet <corbet@lwn.net>
Subject: Re: [PATCH] Documentation: Use "while" instead of "whilst"
Date: Tue, 20 Nov 2018 12:34:35 +0200 [thread overview]
Message-ID: <87in0sf35w.fsf@intel.com> (raw)
In-Reply-To: <1542625365-21886-1-git-send-email-will.deacon@arm.com>
On Mon, 19 Nov 2018, Will Deacon <will.deacon@arm.com> wrote:
> Whilst making an unrelated change to some Documentation, Linus sayeth:
Reference?
>
> | Afaik, even in Britain, "whilst" is unusual and considered more
> | formal, and "while" is the common word.
> |
> | [...]
> |
> | Can we just admit that we work with computers, and we don't need to
> | use þe eald Englisc spelling of words that most of the world never
> | uses?
>
> dictionary.com refers to the word as "Chiefly British", which is
> probably an undesirable attribute for technical documentation.
>
> Replace all occurrences under Documentation/ with "while".
It's an innocent enough change I guess... but seriously? Do we now need
a documentation style guide too...? Should we block an otherwise good
patch with "whilst" in it from now on?
Personally, I'd accept that our documentation is a hodge podge of
regional dialects, written by native and non-native speakers with
incredibly diverse backgrounds and different levels of education and
experience. If we can keep the documentation understandable and mostly
typo free, I'd be happy. Even good grammar seems to be a stretch
goal... ;)
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2018-11-20 10:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-19 11:02 [PATCH] Documentation: Use "while" instead of "whilst" Will Deacon
2018-11-20 10:34 ` Jani Nikula [this message]
2018-11-20 10:46 ` Will Deacon
2018-11-20 16:32 ` Jonathan Corbet
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=87in0sf35w.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=corbet@lwn.net \
--cc=dhowells@redhat.com \
--cc=lgirdwood@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhalcrow@google.com \
--cc=will.deacon@arm.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 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).