From: Matt LaPlante <laplam@rpi.edu>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org, zippel@linux-m68k.org
Subject: Re: [PATCH] Kconfig: Typos in fs/Kconfig
Date: Thu, 29 Jun 2006 13:15:37 -0400 [thread overview]
Message-ID: <20060629131537.49617197.laplam@rpi.edu> (raw)
In-Reply-To: <1151582979.23785.27.camel@localhost.localdomain>
On Thu, 29 Jun 2006 13:09:39 +0100
Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> Ar Iau, 2006-06-29 am 02:00 -0400, ysgrifennodd Matt LaPlante:
> > Fix several typos in fs/Kconfig
>
> Some wrong, some right.
>
> > - tristate "Ext3 journalling file system support"
> > + tristate "Ext3 journaling file system support"
>
> There is actually no such word in the dictionaries I have access to
> (including the OED). An -ing form would be "-lling" in British English
> and ext3 is maintained in the UK which is probably why it uses "lling".
> This was discussed at length about three years ago and the lling was the
> decision taken at the end of the thread.
Opposite here with my upstart American English references. :)
>
> > select JBD
> > help
> > This is the journaling version of the Second extended file system
>
> That one ought to get fixed instead if anything to be consistent.
This version was actually used several times in the KConfig as well. (See below)
>
> > @@ -831,7 +831,7 @@
> >
> > Some system agents rely on the information in sysfs to operate.
> > /sbin/hotplug uses device and object attributes in sysfs to assist in
> > - delegating policy decisions, like persistantly naming devices.
> > + delegating policy decisions, like persistently naming devices.
>
> Persistantly is also correct. Both forms are valid English
>
> > - levelling, compression and support for hard links. You cannot use
> > + leveling, compression and support for hard links. You cannot use
>
> levelling with double ll is also correct English. Single "l" is an
> Americanism. Please stop trying to "Americanise" the Kconfig files and
> just fix actual errors.
>
^Both are reverted. I can honestly say I'm in no way attempting to Americanise/Americanize the files or the kernel...I've intentionally passed by all the spellings I found to be valid in either Engish (Colour/Color, -ise vs -ize for example). My reference dictionaries, which I will be changing now, were apparently more biased than I thought (they did support *some* british english). English is complicated enough on either side of the pond, and when you combine the two you've got a whole new source of chaos and confusion. I'm just trying to correct real mistakes, and I appologize if I err along the way.
The updated patch is below.
-
Matt LaPlante
--
--- a/fs/Kconfig 2006-06-29 02:05:52.000000000 -0400
+++ b/fs/Kconfig 2006-06-29 13:01:35.000000000 -0400
@@ -72,11 +72,11 @@
tristate "Ext3 journalling file system support"
select JBD
help
- This is the journaling version of the Second extended file system
+ This is the journalling version of the Second extended file system
(often called ext3), the de facto standard Linux file system
(method to organize files on a storage device) for hard disks.
- The journaling code included in this driver means you do not have
+ The journalling code included in this driver means you do not have
to run e2fsck (file system checker) on your file systems after a
crash. The journal keeps track of any changes that were being made
at the time the system crashed, and can ensure that your file system
@@ -141,7 +141,7 @@
config JBD
tristate
help
- This is a generic journaling layer for block devices. It is
+ This is a generic journalling layer for block devices. It is
currently used by the ext3 and OCFS2 file systems, but it could
also be used to add journal support to other file systems or block
devices such as RAID or LVM.
@@ -181,7 +181,7 @@
tristate "Reiserfs support"
help
Stores not just filenames but the files themselves in a balanced
- tree. Uses journaling.
+ tree. Uses journalling.
Balanced trees are more efficient than traditional file system
architectural foundations.
@@ -1039,7 +1039,7 @@
tristate "Journalling Flash File System (JFFS) support"
depends on MTD
help
- JFFS is the Journaling Flash File System developed by Axis
+ JFFS is the Journalling Flash File System developed by Axis
Communications in Sweden, aimed at providing a crash/powerdown-safe
file system for disk-less embedded devices. Further information is
available at (<http://developer.axis.com/software/jffs/>).
@@ -1209,7 +1209,7 @@
config JFFS2_CMODE_PRIORITY
bool "priority"
help
- Tries the compressors in a predefinied order and chooses the first
+ Tries the compressors in a predefined order and chooses the first
successful one.
config JFFS2_CMODE_SIZE
@@ -1892,7 +1892,7 @@
If you say Y here, you will get an experimental Andrew File System
driver. It currently only supports unsecured read-only AFS access.
- See <file:Documentation/filesystems/afs.txt> for more intormation.
+ See <file:Documentation/filesystems/afs.txt> for more information.
If unsure, say N.
next prev parent reply other threads:[~2006-06-29 17:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-29 6:00 Matt LaPlante
2006-06-29 7:20 ` Randy.Dunlap
2006-06-29 7:24 ` Matt LaPlante
2006-06-29 12:09 ` Alan Cox
2006-06-29 17:15 ` Matt LaPlante [this message]
2006-06-29 21:59 ` Alan Cox
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=20060629131537.49617197.laplam@rpi.edu \
--to=laplam@rpi.edu \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=zippel@linux-m68k.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®