From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jan Kara <jack@suse.cz>,
linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: [PATCH] ext3: Fix typos in messages and comments (journalled -> journaled)
Date: Wed, 30 Apr 2008 21:27:11 +0100 [thread overview]
Message-ID: <20080430212711.168bdcc0@core> (raw)
In-Reply-To: <20080430104330.66c44d4f.akpm@linux-foundation.org>
On Wed, 30 Apr 2008 10:43:30 -0700
Andrew Morton <akpm@linux-foundation.org> wrote:
> On Wed, 30 Apr 2008 17:06:15 +0200
> Jan Kara <jack@suse.cz> wrote:
>
> > - "EXT3-fs: Cannot change journalled "
> > + "EXT3-fs: Cannot change journaled "
>
> hrm, who said?
This has come up several times before so I thought it might be time to
finally dig to the bottom of the pile and end it forever.
I put on my library hat and went for a dig: the verb is in fact "to
journalize", which according to the OED means
"enter (notes or information) in a journal"
Journal itself is strictly a noun. Thus in English it would be correct
for a file system to have a journal (from the latin diurnalis if anyone
cares) but it would appear that it is a journalizing file system.
The American dictionaries appear to agree with this viewpoint.
If we regard "journalizing" as incorrect then the natural way to end the
word would be -lled for British English and -led would certainly sound
and feel wrong. Indeed the search for the OED turns journalled into
journal when guessing near words but refuses to consider journaled. Our
existing policy is not to mess with US v UK v AU v CA v .. spelling
and that is probably wise.
A search of the ACM literature finds "journalized", "journalled" and
"journaled" are all in use for this operation.
I would submit the correct patch is to change the words to journalizing
and journalized. That would put Linux in agreement with the dictionary,
avoid US v UK meaning differences and not pose a problem linguistically
as all forms are currently in use.
Alan
next prev parent reply other threads:[~2008-04-30 20:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 15:06 [PATCH] ext3: Fix synchronization of quota files in journal=data mode Jan Kara
2008-04-30 15:06 ` [PATCH] ext4: " Jan Kara
[not found] ` <12095679812452-git-send-email-jack@suse.cz>
2008-04-30 15:06 ` [PATCH] ext3: Fix typos in messages and comments (journalled -> journaled) Jan Kara
2008-04-30 15:06 ` [PATCH] ext4: " Jan Kara
[not found] ` <12095679812717-git-send-email-jack@suse.cz>
[not found] ` <12095679824183-git-send-email-jack@suse.cz>
2008-04-30 15:06 ` [PATCH] ext3: Correct mount option parsing to detect when quota options can be changed Jan Kara
2008-04-30 15:06 ` [PATCH] ext4: " Jan Kara
2008-04-30 17:43 ` [PATCH] ext3: Fix typos in messages and comments (journalled -> journaled) Andrew Morton
2008-04-30 20:27 ` Alan Cox [this message]
2008-04-30 22:02 ` Dave Kleikamp
2008-04-30 23:20 ` Alan Cox
2008-05-01 2:28 ` Dave Kleikamp
2008-05-01 9:47 ` Alan Cox
2008-05-01 10:01 ` Joe Fegan
2008-05-03 6:32 ` SL Baur
2008-05-05 10:09 ` Jan Kara
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=20080430212711.168bdcc0@core \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@linux-foundation.org \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).