[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4646C8FA.2090602@adacore.com>
Date: Sun, 13 May 2007 04:14:50 -0400
From: Robert Dewar <dewar@...core.com>
To: James Cloos <cloos@...loos.com>
CC: LKML <linux-kernel@...r.kernel.org>, discuss@...-64.org,
trivial@...nel.org, Andi Kleen <ak@...e.de>,
Simon Arlott <simon@...e.lp0.eu>
Subject: Re: [discuss] [PATCH] spelling fixes: arch/x86_64/
James Cloos wrote:
>>>>>> "Andi" == Andi Kleen <ak@...e.de> writes:
>
>>> - /* Reenable any watchpoints before delivering the
>>> + /* Re-enable any watchpoints before delivering the
>
> Andi> reenable gets >140k google hits so it seems to be an really
> Andi> used word.
Well you will find extensive "misuse" of all the re-e* words in
english, but all should be hyphenated. Moreover, there is no
license in english to just create new such words, you cannot
re-entertain your guests for example. In practice we do allow
creation of new re-e* words, as in re-execute, and that's
probably ok in techno-jargon-speak.
But re-enable is an old and well used word, reenable is not,
and I see no reason to encourage the latter incorrect use,
since it is harder to read (double e after r at the start
of the word is almost always a long e).
Note that in google, you always want to hyphenate. reenable
will catch only the misuses, re-enable will catch both.
>
> Essentially all commonly used English words which start out with hyphens
> loose them over time. It starts out with typos and progresses until the
> non-hyphenated form becomes the exclusively used form. It does seem that
> re-enable → reenable is occurring, based on those search hits.
Hyphens do sometimes disappear, but not for re-e*, OED version
2 does not allow a single such instance.
>
> Andi> Similar with upto.
>
> I’ve a *much* harder time agreeing with «upto» in place of «up to».
> That should be treated as a typo in need of fixing.
Indeed .. upto is not a word.
>
> -JimC
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists