From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:42064) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RQ2ch-0001Nj-QC for qemu-devel@nongnu.org; Mon, 14 Nov 2011 14:55:20 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RQ2cg-0007dB-9g for qemu-devel@nongnu.org; Mon, 14 Nov 2011 14:55:19 -0500 Received: from v220110690675601.yourvserver.net ([78.47.199.172]:48244) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RQ2cg-0007d6-32 for qemu-devel@nongnu.org; Mon, 14 Nov 2011 14:55:18 -0500 Message-ID: <4EC171FC.4070103@weilnetz.de> Date: Mon, 14 Nov 2011 20:54:36 +0100 From: Stefan Weil MIME-Version: 1.0 References: <4EC16971.5030209@weilnetz.de> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 1.0 2/2] Fix some spelling bugs in documentation and comments List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: QEMU Developers Am 14.11.2011 20:25, schrieb Peter Maydell: > On 14 November 2011 19:18, Stefan Weil wrote: >> --- a/docs/libcacard.txt >> +++ b/docs/libcacard.txt >> @@ -281,7 +281,7 @@ create card responses. >> VCardResponse *vcard_make_response(VCard7816Status status); >> >> This is the most basic function to get a response. This function will >> - return a response the consists soley one 2 byte status code. If that >> status >> + return a response the consists solely one 2 byte status code. If >> that >> status > > "return a response that consists solely of one 2 byte status code" > >> code is defined in card_7816t.h, then this function is guarrenteed to > > "guaranteed" > >> return a response with that status. If a cart type specific >> status code > > "card type" > > -- PMM I noticed these, too - see my mail: "libcacard.txt still needs some more patches", but was not sure about the first one. Thanks for your feedback. It's always good to have a native speaker who shows us foreigners the right way of writing :-) The file still needs more patches even after your changes (e.g. replacable), so I suggest that we proceed incrementally: first my patch, then your patch, then whoever wants ... --- SW