The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Matt LaPlante <kernel1@cyberdogtech.com>
Cc: linux-kernel@vger.kernel.org, trivial@kernel.org
Subject: Re: [PATCH 18-rc2] Fix "can not" in Documentation and Kconfig
Date: Wed, 26 Jul 2006 21:08:15 -0700	[thread overview]
Message-ID: <20060726210815.0fbfc012.rdunlap@xenotime.net> (raw)
In-Reply-To: <20060726192029.173c89b6.kernel1@cyberdogtech.com>

On Wed, 26 Jul 2006 19:20:29 -0400 Matt LaPlante wrote:

> Randy brought it to my attention that in proper english "can not" should always be written "cannot". I donot see any reason to argue, even if I mightnot understand why this rule exists.  This patch fixes "can not" in several Documentation files as well as three Kconfigs.
> 
> Signed-off-by: Matt LaPlante <kernel1@cyberdogtech.com>
> --

Thanks, Matt.

Acked-by: Randy Dunlap <rdunlap@xenotime.net>

---
~Randy

      reply	other threads:[~2006-07-27  4:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-26 23:20 [PATCH 18-rc2] Fix "can not" in Documentation and Kconfig Matt LaPlante
2006-07-27  4:08 ` 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=20060726210815.0fbfc012.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=kernel1@cyberdogtech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trivial@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