From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IApum-0002od-5m for qemu-devel@nongnu.org; Tue, 17 Jul 2007 12:28:44 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IApuk-0002oR-KG for qemu-devel@nongnu.org; Tue, 17 Jul 2007 12:28:42 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IApuk-0002oO-Ej for qemu-devel@nongnu.org; Tue, 17 Jul 2007 12:28:42 -0400 Received: from an-out-0708.google.com ([209.85.132.249]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IApuk-0003cx-2m for qemu-devel@nongnu.org; Tue, 17 Jul 2007 12:28:42 -0400 Received: by an-out-0708.google.com with SMTP id d11so465289and for ; Tue, 17 Jul 2007 09:28:41 -0700 (PDT) Message-ID: Date: Tue, 17 Jul 2007 09:28:41 -0700 From: "Jonathan Kalbfeld" Subject: Re: [Qemu-devel] More misspellings In-Reply-To: <20070717150423.GA16468@miranda.arrow> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_96601_31666742.1184689721127" References: <20070717150423.GA16468@miranda.arrow> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org ------=_Part_96601_31666742.1184689721127 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline I should send you my grad school papers to spellcheck :) On 7/17/07, 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.) > > 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 ------=_Part_96601_31666742.1184689721127 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 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 ------=_Part_96601_31666742.1184689721127--