From: Junio C Hamano Date: Thu, 05 Feb 2015 19:29:07 GMT Subject: Re: [Qemu-devel] [PATCH v3 0/7] cpu: add device_add foo-x86_64-cpu support Message-ID: In-Reply-To: <54D38B73.4060803@redhat.com> Eric Blake writes: > 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 >> >> This email has an invalid charset: >> Content-Type: text/plain; charset="y" >> >> I guess you entered "y" when asked how the message was encoded. >> >> 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? I think I answered this in $gmane/263354; care to come up with a plausible valid_re? It is inpractical to attempt to cover all valid charset names, so whatever you do I'd imagine you would want to pass the confirm_only parameter set to true.