From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Matt LaPlante <laplam@rpi.edu>
Cc: linux-kernel@vger.kernel.org, Roman Zippel <zippel@linux-m68k.org>
Subject: Re: [PATCH] Kconfig: Typos in fs/Kconfig
Date: Thu, 29 Jun 2006 13:09:39 +0100 [thread overview]
Message-ID: <1151582979.23785.27.camel@localhost.localdomain> (raw)
In-Reply-To: <20060629020052.f73d7ca1.laplam@rpi.edu>
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.
> 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.
> @@ -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.
> config JFFS2_CMODE_PRIORITY
> bool "priority"
> help
> - Tries the compressors in a predefinied order and chooses the first
Appears to be a genuine fix
>
> 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.
Likewise
next prev parent reply other threads:[~2006-06-29 11:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-29 6:00 [PATCH] Kconfig: Typos in fs/Kconfig Matt LaPlante
2006-06-29 7:20 ` Randy.Dunlap
2006-06-29 7:24 ` Matt LaPlante
2006-06-29 12:09 ` Alan Cox [this message]
2006-06-29 17:15 ` Matt LaPlante
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=1151582979.23785.27.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=laplam@rpi.edu \
--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