From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:38066) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1THJWW-0007XI-BY for qemu-devel@nongnu.org; Thu, 27 Sep 2012 15:13:28 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1THJWQ-0008Uk-K4 for qemu-devel@nongnu.org; Thu, 27 Sep 2012 15:13:24 -0400 Message-ID: <5064A546.9080302@redhat.com> Date: Thu, 27 Sep 2012 13:13:10 -0600 From: Eric Blake MIME-Version: 1.0 References: <1348772258-31168-1-git-send-email-sw@weilnetz.de> In-Reply-To: <1348772258-31168-1-git-send-email-sw@weilnetz.de> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------enig201D6CFB87E5688DF357DBD8" Subject: Re: [Qemu-devel] [PATCH] slirp: Fix spelling in comment (enought -> enough, insure -> ensure) List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Weil Cc: qemu-trivial@nongnu.org, Jan Kiszka , qemu-devel@nongnu.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig201D6CFB87E5688DF357DBD8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 09/27/2012 12:57 PM, Stefan Weil wrote: > Signed-off-by: Stefan Weil > --- >=20 > As a non native speaker, I feel that 'ensure' is better here than 'insu= re'. > Could a native speaker please confirm that? As a US speaker, I've seen both words used interchangeably. I also checked dictionary.com, where both words imply a guarantee, but 'insure' has a connotation of a guarantee against loss (think insurance policy) while 'ensure' tends to be used in most other situations. That is, I am in favor of this spelling change for connotation reasons. But as Peter pointed out, the sentence has more problems than just a spelling choice. > - * For the error advice packets must first insure that the > - * packet is large enought to contain the returned ip header. > + * For the error advice packets must first ensure that the > + * packet is large enough to contain the returned ip header. > * Only then can we do the check to see if 64 bits of packet > * data have been returned, since we need to check the returned > * ip header length. >=20 --=20 Eric Blake eblake@redhat.com +1-919-301-3266 Libvirt virtualization library http://libvirt.org --------------enig201D6CFB87E5688DF357DBD8 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Public key at http://people.redhat.com/eblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iQEcBAEBCAAGBQJQZKVGAAoJEKeha0olJ0Nq6ccIAKZrEhz04M6hj0YvsKhjbZ6T IMQcW8xgxjdVIFBwir7QM6IrkGa5h0HnpK33tRqhnyCZjnnUedd0dnJ+jEFTQz2P SGvZwKsYMp9SIs2rQehe/HpqqFfb2fN8no8iF2KXvFc96bQERUySy/S1IXmYqSY2 3h0hok3S31VWfikb21E0Q8yZre9gZeN16OuOtlEErVFG/GcPfDll2P8Jficlgdj0 QFp7CBknnjPLZvDo0ELc9aL/zIEBHxZi1SzSPqy2G60o0ESNbntO2/RwjVy4bIjR GOAV1ygEDcerHvelT9Axd5+md73IhhZAEN/JCH81ZlNU5JGdSbg0RAsw9kv9bwQ= =RW0S -----END PGP SIGNATURE----- --------------enig201D6CFB87E5688DF357DBD8--