From: Dave Kleikamp <shaggy@linux.vnet.ibm.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Andrew Morton <akpm@linux-foundation.org>,
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:28:07 -0500 [thread overview]
Message-ID: <1209608887.7650.6.camel@norville.austin.ibm.com> (raw)
In-Reply-To: <20080501002018.2729adcc@core>
On Thu, 2008-05-01 at 00:20 +0100, Alan Cox wrote:
> > > A search of the ACM literature finds "journalized", "journalled" and
> > > "journaled" are all in use for this operation.
> >
> > I hate to get into these discussions, but I've used "journaled" a lot,
> > so I feel I should chime in.
>
> I noticed and IBM cannot even agree internally 8)
>
> "Tivoli Storage Manager Journal Based Backup troubleshooting techniques
> and solutions to common problems seen with journalized backups and the
> journal database. This is from a 2005_November_07 Support Technical
> Exchange Web seminar presented by TSM Support staff"
>
> "IBM Journaled File System (JFS)"
IBM's big. What can I say? :-)
> > That would probably be more correct, but the use of "journal" as a verb
> > has really gotten ingrained in file system developers brains. I
> > personally haven't heard or used "journalized" and it would take some
> > getting used to.
>
> Mandrake use Journalized File System in various press articles. Mac
> people seem to like journalized too and google shows it used in various
> reviews and articles.
I guess it's more common that I thought.
> I think I'm going to follow this up with the professional bodies and see
> if there is an opinion because either the computing world needs to agree
> on a proper English name, or they need to agree on a new one and talk to
> the dictionary people about it.
If there's some kind of consensus, I don't have strong feelings either
way.
--
David Kleikamp
IBM Linux Technology Center
next prev parent reply other threads:[~2008-05-01 2:28 UTC|newest]
Thread overview: 21+ 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
2008-04-30 15:06 ` [PATCH] reiserfs: " Jan Kara
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
2008-04-30 15:06 ` [PATCH] reiserfs: " Jan Kara
2008-04-30 15:06 ` [PATCH] quota: Add a convenience macro for filesystems Jan Kara
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 15:06 ` [PATCH] reiserfs: " Jan Kara
2008-04-30 19:29 ` [PATCH] quota: Add a convenience macro for filesystems Andrew Morton
2008-05-05 10:01 ` 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
2008-04-30 22:02 ` Dave Kleikamp
2008-04-30 23:20 ` Alan Cox
2008-05-01 2:28 ` Dave Kleikamp [this message]
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=1209608887.7650.6.camel@norville.austin.ibm.com \
--to=shaggy@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--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
all inboxes | Powered by JetHome®