From: Frans Pop <elendil@planet.nl>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hfsplus: Correct user visible printk
Date: Fri, 2 May 2008 17:42:49 +0200 [thread overview]
Message-ID: <200805021742.50509.elendil@planet.nl> (raw)
In-Reply-To: <20080502150439.76beaf27@core>
On Friday 02 May 2008, Alan Cox wrote:
> > BTW, what is common spelling in the kernel British or American English?
>
> It varies. The fs journal code uses both at random sometimes mixed in the
> same paragraph. Fortunately "to journalise" is valid in both US and UK
> English.
Well, my spellchecker rejects the -se but recognizes the -ze. It also has no
problems with journaled.
> > journaled: 134,000 hits ( 8.7% of above total)
>
> Almost entirely caused by Linux.
Sure. But that only proves my point: once something has been accepted as
common language and a term, however technically wrong, is recognized to
stand for something by the majority of existing users, it is probably wrong
to change it. After all, language is a living and evolving thing. This is
exactly how new words, terms and simplifications are introduced.
Google clearly shows that journaled is the accepted, and thus preferred
term. Maybe if you'd proposed this patch (and others everywhere else
journaled has been used) 5 years ago you'd been right. At this stage I
think a change would only confuse.
Cheers,
FJP
next prev parent reply other threads:[~2008-05-02 15:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-02 13:29 [PATCH] hfsplus: Correct user visible printk Alan Cox
2008-05-02 14:00 ` Frans Pop
2008-05-02 14:04 ` Alan Cox
2008-05-02 15:42 ` Frans Pop [this message]
2008-05-02 15:44 ` Alan Cox
2008-05-02 21:18 ` Jeremy Fitzhardinge
2008-05-02 22:29 ` Alan Cox
2008-05-03 11:49 ` SL Baur
2008-05-03 12:06 ` Frans Pop
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=200805021742.50509.elendil@planet.nl \
--to=elendil@planet.nl \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox