[Qemu-devel] More misspellings

[Qemu-devel] More misspellings

[Stuart Brady]

Hi,

I spellchecked much of QEMU's source a while ago, and produced a list of 
misspellings, which I now include below.

I could submit a patch to fix these, but I'm not sure what its preferred 
form would be.  Would it be better to submit separate patches for 
changes to the docs and/or strings, or would one big patch be okay?
(Bear in mind I've counted 206 non-distinct misspellings.)

I'll understand if this is deemed too large a cosmetic issue to be worth 
committing anything, but OTOH, it shouldn't be especially disruptive, as 
any merge conflicts would be trivial to fix.

Thanks,
-- 
Stuart Brady

accordin, addresss, amounnt, an a, apear, arbitary, arbritration,
asynchrnonous, autio, begining, choosen, completly, compliation, confition,
decrememnted, defering, dependancy, desciptor, dirst, disconect, enought,
enoutered, epilog, exeption, existant, explicitely, feild, fordward, formwer,
hadle_packet, heplers, immeriately, inconsistancies, indepedent, inspirated,
instruciton, instructon, instrunctions, interrput, interupt_request,
intruction, jup, latters, lenght, mecanism, miniscule, minmal, montior,
neccessary, neeed, negotion, normaly, occured, occuring, olders, overrite,
paramters, parmissible, peripherans, peripherial, positionned, preceeding,
precition, prefech, prefered, presrved, previos, priledge, priveladged,
priveledged, priveleged, priviledge, privledge, psuedo, puting, regiser,
replacd, reservered, ressources, rythm, seconday, shoud, simplicitly, somethin,
spliting, stabalized, succesfully, suppored, supresses, supression, teh,
tranfer, transmiter, trasfer, unknwon, unkown, unstandard, useable, vairable,
weired, whitespaces, writting, yeild

Re: [Qemu-devel] More misspellings

[Jonathan Kalbfeld]

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

I should send you my grad school papers to spellcheck :)

On 7/17/07, Stuart Brady <sdbrady@ntlworld.com> wrote:
>
> Hi,
>
> I spellchecked much of QEMU's source a while ago, and produced a list of
> misspellings, which I now include below.
>
> I could submit a patch to fix these, but I'm not sure what its preferred
> form would be.  Would it be better to submit separate patches for
> changes to the docs and/or strings, or would one big patch be okay?
> (Bear in mind I've counted 206 non-distinct misspellings.)
>
> I'll understand if this is deemed too large a cosmetic issue to be worth
> committing anything, but OTOH, it shouldn't be especially disruptive, as
> any merge conflicts would be trivial to fix.
>
> Thanks,
> --
> Stuart Brady
>
> accordin, addresss, amounnt, an a, apear, arbitary, arbritration,
> asynchrnonous, autio, begining, choosen, completly, compliation,
> confition,
> decrememnted, defering, dependancy, desciptor, dirst, disconect, enought,
> enoutered, epilog, exeption, existant, explicitely, feild, fordward,
> formwer,
> hadle_packet, heplers, immeriately, inconsistancies, indepedent,
> inspirated,
> instruciton, instructon, instrunctions, interrput, interupt_request,
> intruction, jup, latters, lenght, mecanism, miniscule, minmal, montior,
> neccessary, neeed, negotion, normaly, occured, occuring, olders, overrite,
> paramters, parmissible, peripherans, peripherial, positionned, preceeding,
> precition, prefech, prefered, presrved, previos, priledge, priveladged,
> priveledged, priveleged, priviledge, privledge, psuedo, puting, regiser,
> replacd, reservered, ressources, rythm, seconday, shoud, simplicitly,
> somethin,
> spliting, stabalized, succesfully, suppored, supresses, supression, teh,
> tranfer, transmiter, trasfer, unknwon, unkown, unstandard, useable,
> vairable,
> weired, whitespaces, writting, yeild
>
>
>


-- 
--
Jonathan Kalbfeld
+1 323 620 6682

[-- Attachment #2: Type: text/html, Size: 2283 bytes --]

Re: [Qemu-devel] More misspellings

[Thiemo Seufer]

Stuart Brady wrote:
> Hi,
> 
> I spellchecked much of QEMU's source a while ago, and produced a list of 
> misspellings, which I now include below.
> 
> I could submit a patch to fix these, but I'm not sure what its preferred 
> form would be.  Would it be better to submit separate patches for 
> changes to the docs and/or strings, or would one big patch be okay?
> (Bear in mind I've counted 206 non-distinct misspellings.)

Make it a set of patches, split per-file (or per group-of-files if they
were tiny otherwise).


Thiemo