From: Matt LaPlante <kernel1@cyberdogtech.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
akpm@osdl.org, Linus Torvalds <torvalds@osdl.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Fix typos in doc and comments (1)
Date: Tue, 17 Oct 2006 01:22:09 -0400 [thread overview]
Message-ID: <20061017012209.c764a3ec.kernel1@cyberdogtech.com> (raw)
In-Reply-To: <20061016160738.2199bbcb.rdunlap@xenotime.net>
On Mon, 16 Oct 2006 16:07:38 -0700
Randy Dunlap <rdunlap@xenotime.net> wrote:
> On Tue, 17 Oct 2006 00:50:56 +0200 (MEST) Jan Engelhardt wrote:
>
> >
> >
> > Changes persistant -> persistent. www.dictionary.com does not know
> > persistant (with an A), but should it be one of those things you can
> > spell in more than one correct way, let me know.
>
> I agree with it, but IIRC Alan said it could be either way.
>
While I also agree, you're correct about Alan's claim. He used a print dictionary...I've yet to find an online dictionary that supports this spelling. (Note: I've found m-w.com to be the best at catching both British English and American English spellings. Cambridge online is good too).
> > Index: linux-2.6.19-rc2/lib/textsearch.c
> > ===================================================================
> > --- linux-2.6.19-rc2.orig/lib/textsearch.c
> > +++ linux-2.6.19-rc2/lib/textsearch.c
> > @@ -40,7 +40,7 @@
> > * configuration according to the specified parameters.
> > * (3) User starts the search(es) by calling _find() or _next() to
> > * fetch subsequent occurrences. A state variable is provided
> > - * to the algorihtm to store persistant variables.
> > + * to the algorihtm to store persistent variables.
>
> fix /algorithm/ while here?
> or did Matt already fix that one?
>
I haven't yet submitted typo fixes to any c/h files, so no. I actually do have a c/h file patch done and pending from a couple days ago, I just haven't mailed it yet.
> > * (4) Core eventually resets the search offset and forwards the find()
> > * request to the algorithm.
> > * (5) Algorithm calls get_next_block() provided by the user continously
>
> ---
> ~Randy
--
Matt
next prev parent reply other threads:[~2006-10-17 5:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-16 22:50 [PATCH] Fix typos in doc and comments (1) Jan Engelhardt
2006-10-16 23:00 ` [PATCH] Fix typos in doc and comments (2) Jan Engelhardt
2006-10-16 23:07 ` [PATCH] Fix typos in doc and comments (1) Randy Dunlap
2006-10-17 5:22 ` Matt LaPlante [this message]
2006-10-17 13:17 ` 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=20061017012209.c764a3ec.kernel1@cyberdogtech.com \
--to=kernel1@cyberdogtech.com \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.