From: Dave Jones <davej@codemonkey.org.uk>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Spelling fixes for consistent, dependent, persistent
Date: Sun, 9 Feb 2003 15:13:20 +0000 [thread overview]
Message-ID: <20030209151320.GB12877@codemonkey.org.uk> (raw)
In-Reply-To: <200302090902.h1992KJ05999@hera.kernel.org>
On Fri, Feb 07, 2003 at 04:11:08PM +0000, Linux Kernel wrote:
> ChangeSet 1.999, 2003/02/07 08:11:08-08:00, elenstev@mesatop.com
>
> [PATCH] Spelling fixes for consistent, dependent, persistent
>
> This fixes the following common misspellings and their variants.
>
> consistant -> consistent
> dependant -> dependent
> persistant -> persistent
>
> <snip 83K patch>
Can we hold off on tree-wide 'corrections' like this until we at least
get closer to 2.6-test ? Doing these at this point in time really
screws over a lot of out-of-tree patches.
Oh, and Dependant is an allowed variation btw.[1][2]
Dave
[1] http://www.m-w.com/cgi-bin/dictionary?va=dependant
[2] http://dictionary.reference.com/search?q=Dependant
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
parent reply other threads:[~2003-02-09 15:07 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <200302090902.h1992KJ05999@hera.kernel.org>]
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=20030209151320.GB12877@codemonkey.org.uk \
--to=davej@codemonkey.org.uk \
--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;
as well as URLs for NNTP newsgroup(s).