From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:42879) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YJPrq-0000B0-8j for qemu-devel@nongnu.org; Thu, 05 Feb 2015 12:05:27 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YJPrn-0001F5-6n for qemu-devel@nongnu.org; Thu, 05 Feb 2015 12:05:26 -0500 Received: from mx1.redhat.com ([209.132.183.28]:53334) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YJPrm-0001Eo-UK for qemu-devel@nongnu.org; Thu, 05 Feb 2015 12:05:23 -0500 Message-ID: <54D38B73.4060803@redhat.com> Date: Thu, 05 Feb 2015 08:25:39 -0700 From: Eric Blake MIME-Version: 1.0 References: <20150205114914.GA10126@stefanha-thinkpad.redhat.com> In-Reply-To: <20150205114914.GA10126@stefanha-thinkpad.redhat.com> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="vJVjbNUh2u8Cm4C2l7EKWuvU6V8d5oPi9" Subject: Re: [Qemu-devel] [PATCH v3 0/7] cpu: add device_add foo-x86_64-cpu support List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Stefan Hajnoczi , Zhu Guihua Cc: qemu-devel@nongnu.org, tangchen@cn.fujitsu.com, guz.fnst@cn.fujitsu.com, isimatu.yasuaki@jp.fujitsu.com, anshul.makkar@profitbricks.com, chen.fan.fnst@cn.fujitsu.com, imammedo@redhat.com, afaerber@suse.de, git@vger.kernel.org This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --vJVjbNUh2u8Cm4C2l7EKWuvU6V8d5oPi9 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable [adding git list to cc] On 02/05/2015 04:49 AM, Stefan Hajnoczi wrote: > On Wed, Jan 14, 2015 at 03:27:23PM +0800, Zhu Guihua wrote: >> This series is based on the previous patchset from Chen Fan: >> https://lists.nongnu.org/archive/html/qemu-devel/2014-05/msg02360.html= >=20 > This email has an invalid charset: > Content-Type: text/plain; charset=3D"y" >=20 > I guess you entered "y" when asked how the message was encoded. >=20 > Please don't do that, it means we can only guess at the charset. In the past, people made a similar problem when 'git send-email' was asking if a message was in-reply-to something else (the number of messages incorrectly threaded to a message-id of 'y' or 'n' was evidence of the poor quality of the question). git.git commit 51bbccfd1b4a corrected that problem. Sounds like charset encoding is another case where the interactive parser should be taught to balk at nonsense encoding answers? --=20 Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org --vJVjbNUh2u8Cm4C2l7EKWuvU6V8d5oPi9 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 Comment: Public key at http://people.redhat.com/eblake/eblake.gpg Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCAAGBQJU04tzAAoJEKeha0olJ0NqukEH/R0mHwErOYfjPiISU76SpjXU O9wxnaqwWh5vONIHz3z0bX6LFuECyRS51yCrqsSeHh8MUBTPv0by3083/akBPrcg Mqtc15rlsR1p2iaJ7n3CBaPwcIPHxmsUn8JVB4L+a133cmj/8XhhKjmen3gKvuh3 B1YQkPQrn/hGOVw/lLYkWXxweqdLGRdWDXoo6CrO5uyVqnWyPujDaVE4nNAxO1Ri qsAzaoeCoW7WCnfkGe0DKOQ6bK+ueL/7oerZiVRR1T9RRNNOSufsrGplApOEXPus k/BY32OWQjheJPoBWk7WHMDAcfehS/mKBb221+BItKPReNEliTRkiHtTo7JZ7Bg= =so7v -----END PGP SIGNATURE----- --vJVjbNUh2u8Cm4C2l7EKWuvU6V8d5oPi9--