linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Kegel <dank@kegel.com>
To: Joe Perches <joe@perches.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] kernel source spellchecker
Date: Fri, 28 Feb 2003 21:38:20 -0800	[thread overview]
Message-ID: <3E60474C.1060304@kegel.com> (raw)
In-Reply-To: <1046330232.15763.97.camel@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 905 bytes --]

Joe Perches wrote:
> On Wed, 2003-02-26 at 22:59, Dan Kegel wrote:
> 
>>Since the main remaining feature before release of the 2.6
>>kernel is fixing all the remaining spelling errors,
>>this patch seems appropriate. 
> 
> 
> Who let the comedian in? :o

At first I was jokeing, but what the heck, I figured I'd run
it.  Here are the mispelled words that occur in five
or more files and that lookd like real misspellings to my eye.
The list contains some words that are ok in British usage;
I don't have a British spellchecker (that I know how to use).

Perhaps some eagr Perl monger can (after removing the British-ok
words!) contribute a spellcorrect-kernel program that takes
in a liste of known misspellings + corrections, and applies
them to the commments in all kernel source files...
- Dan



-- 
Dan Kegel
http://www.kegel.com
http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045

[-- Attachment #2: errors.txt --]
[-- Type: text/plain, Size: 1813 bytes --]

accomodate
Acknowledgement
acknowledgements
adaptor
adaptors
adddress
additionnal
alignement
allways
analyse
angerous
apropriate
arround
assosciated
assosiated
asyncronous
Auxillary
availible
avaliable
basicly
beeing
borken
boundry
bramaged
cacheable
callin
cancelled
capabilites
childs
choosen
comamnd
comming
commited
comparision
Compatability
compatibilty
compatiblity
completly
concurent
Continous
continous
controler
controllen
coresponding
decrementer
decriptor
defered
defintions
denormalised
denormalized
dependend
desciptor
devide
differenciate
doesnt
DONT
dont't
dugger
emptive
entrancy
entrys
everytime
explicitely
foward
fuction
funtion
guarenteed
handeling
harware
hasnt
havn't
houldn't
hysical
i'm
immediatly
implemantation
implmentation
Incomming
incomming
indice
infomation
Inifity
inital
initalization
Initalize
initalize
inited
initilization
initing
inteface
interrrupt
interrups
Interupt
intervall
intialization
Intialize
intialize
invokation
is'nt
Lenght
managment
mergeable
middelin
modelled
Modularisation
modularisation
Modularised
neccessary
negociated
Neighbour
neighbour
Noone
nuclecu
occured
occurence
occuring
organised
ouput
outputing
overriden
paramter
paramters
Passthrough
passthru
performace
popies
preceeding
promiscous
realise
realised
receving
Recieve
recieve
recieved
recognised
reenable
reentrance
registred
Regsiter
relevent
Reorganisation
reorganised
requeue
reselection
resetted
ressources
scather
serialisation
shouldnt
signalled
signalling
sleepie
specifc
specifed
speficied
sublicense
succesful
successfull
superflous
Synchronisation
synchronisation
there're
threshhold
throught
thru
timming
TORTIOUS
tranceiver
transfering
transmiting
trasfered
truely
tunables
uffer
uglyness
uncachable
unrecognised
useable
usefull
verticies
waranty
watseful
wierd
writeable
writting

  parent reply	other threads:[~2003-03-01  5:18 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-27  6:59 [PATCH] kernel source spellchecker Dan Kegel
     [not found] ` <1046330232.15763.97.camel@localhost.localdomain>
2003-03-01  5:38   ` Dan Kegel [this message]
2003-03-01 14:11     ` Matthias Schniedermeyer
2003-03-01 17:13       ` Matthias Schniedermeyer
2003-03-01 18:54       ` Dan Kegel
2003-03-01 19:18         ` Steven Cole
2003-03-01 21:20           ` Dan Kegel
2003-03-02  3:45             ` jw schultz
2003-03-02  2:08           ` Dan Kegel
2003-03-02  3:02             ` Dan Kegel
2003-03-02  3:54               ` Steven Cole
2003-03-02  8:04                 ` Dan Kegel
2003-03-02  4:16               ` Steven Cole
2003-03-02  8:21                 ` Dan Kegel
2003-03-02  8:40                   ` jw schultz
2003-03-02 11:21                 ` David Woodhouse
2003-03-02 13:49                   ` Steven Cole
2003-03-02 14:55                     ` David Woodhouse
2003-03-02 22:44                     ` Alan Cox
2003-03-02 22:59                       ` John Bradford
2003-03-03  2:29                       ` Dan Kegel
     [not found]                     ` <3E62C0FF.1090700@kegel.com>
     [not found]                       ` <1046661777.7527.518.camel@spc1.mesatop.com>
2003-03-03  5:36                         ` Dan Kegel
     [not found]                         ` <3E62E4C0.9070103@kegel.com>
     [not found]                           ` <1046668274.7527.533.camel@spc1.mesatop.com>
2003-03-03  5:48                             ` Dan Kegel
2003-03-02 15:35                   ` Dan Kegel
2003-03-02  8:09               ` Matthias Schniedermeyer
2003-03-02  8:13                 ` Matthias Schniedermeyer
2003-03-02  3:29             ` Steven Cole
2003-03-01 19:30         ` Matthias Schniedermeyer
2003-03-01 20:33           ` Matthias Schniedermeyer
2003-03-01 21:25           ` Dan Kegel
2003-03-01 21:25             ` Matthias Schniedermeyer
2003-03-02  9:15               ` John Bradford
2003-03-02  9:31                 ` Matthias Schniedermeyer
2003-03-02  3:16         ` Horst von Brand
2003-03-01 15:57 shaheed
2003-03-01 16:35 ` Jörn Engel
2003-03-01 18:01   ` shaheed
2003-03-01 18:31     ` Jörn Engel
2003-03-05 18:10   ` Pavel Machek
     [not found] <20030301160017$56fc@gated-at.bofh.it>
2003-03-01 18:39 ` Pascal Schmidt
2003-03-02 18:56 Jared Daniel J. Smith
2003-03-02 17:22 ` Bernd Petrovitsch
2003-03-02 17:47   ` Werner Almesberger
2003-03-02 18:28     ` Bernd Petrovitsch
2003-03-02 18:46 ` Steven Cole
2003-03-02 22:32   ` 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=3E60474C.1060304@kegel.com \
    --to=dank@kegel.com \
    --cc=joe@perches.com \
    --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).