From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Jesper Juhl <juhl-lkml@dif.dk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH][trivial] fix tiny spelling error in init/Kconfig and write "so-called" instead of "so called" and "socalled" everywhere.
Date: Sat, 26 Mar 2005 10:40:51 -0800 [thread overview]
Message-ID: <4245ACB3.1080105@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.62.0503261130550.2437@dragon.hyggekrogen.localhost>
Jesper Juhl wrote:
> On Fri, 25 Mar 2005, Randy.Dunlap wrote:
>
>
>>Jesper Juhl wrote:
>>
>>>Fix spelling in init/Kconfig
>>>
>>>Signed-off-by: Jesper Juhl <juhl-lkml@dif.dk>
>>>
>>>--- linux-2.6.12-rc1-mm3-orig/init/Kconfig 2005-03-25 15:29:08.000000000
>>>+0100
>>>+++ linux-2.6.12-rc1-mm3/init/Kconfig 2005-03-26 02:24:33.000000000 +0100
>>>@@ -83,7 +83,7 @@
>>> default y
>>> help
>>> This option allows you to choose whether you want to have support
>>>- for socalled swap devices or swap files in your kernel that are
>>>+ for so called swap devices or swap files in your kernel that are
>>> used to provide more virtual memory than the actual RAM present
>>> in your computer. If unsure say Y.
>>
>>I would prefer (and write) "so-called".
>>
>
> I believe both "so called" and "so-called" are valid, but "so-called"
> seems to be more common in the Kconfig files already. So let's be
> consistent about it.
>
>
> Signed-off-by: Jesper Juhl <juhl-lkml@dif.dk>
I agree. Thanks.
--
~Randy
prev parent reply other threads:[~2005-03-26 18:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-26 1:26 [PATCH][trivial] fix tiny spelling error in init/Kconfig Jesper Juhl
2005-03-26 3:10 ` Randy.Dunlap
2005-03-26 10:46 ` [PATCH][trivial] fix tiny spelling error in init/Kconfig and write "so-called" instead of "so called" and "socalled" everywhere Jesper Juhl
2005-03-26 18:40 ` Randy.Dunlap [this message]
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=4245ACB3.1080105@osdl.org \
--to=rddunlap@osdl.org \
--cc=juhl-lkml@dif.dk \
--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