linux-kernel - Re: [PATCH] Documentation: Use "while" instead of "whilst"

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 20 Nov 2018 12:34:35 +0200
From:   Jani Nikula <jani.nikula@...ux.intel.com>
To:     Will Deacon <will.deacon@....com>, linux-doc@...r.kernel.org
Cc:     linux-kernel@...r.kernel.org, Will Deacon <will.deacon@....com>,
        David Howells <dhowells@...hat.com>,
        Liam Girdwood <lgirdwood@...il.com>,
        Chris Wilson <chris@...is-wilson.co.uk>,
        Michael Halcrow <mhalcrow@...gle.com>,
        Jonathan Corbet <corbet@....net>
Subject: Re: [PATCH] Documentation: Use "while" instead of "whilst"

On Mon, 19 Nov 2018, Will Deacon <will.deacon@....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