From: "Michael S. Tsirkin" <mst@redhat.com>
To: Eric Blake <eblake@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
mlureau@redhat.com, Fam Zheng <famz@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PULL for-2.9 0/9] virtio, vhost, pc: fixes
Date: Fri, 6 Jan 2017 23:20:10 +0200 [thread overview]
Message-ID: <20170106231922-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <3240188c-69b7-bbc9-6121-a75d093f5289@redhat.com>
On Fri, Jan 06, 2017 at 02:38:32PM -0600, Eric Blake wrote:
> On 01/06/2017 02:04 PM, Michael S. Tsirkin wrote:
> > On Sat, Dec 17, 2016 at 11:18:03AM +0000, Peter Maydell wrote:
> >> On 16 December 2016 at 21:32, <no-reply@patchew.org> wrote:
> >>> Your series seems to have some coding style problems. See output below for
> >>> more information:
> >>>
> >>> Type: series
> >>> Subject: [Qemu-devel] [PULL for-2.9 0/9] virtio, vhost, pc: fixes
> >>> Message-id: 1481922841-4324-1-git-send-email-mst@redhat.com
> >>
> >>> Checking PATCH 5/9: contrib: add libvhost-user...
> >>> ERROR: Invalid UTF-8, patch and commit message should be encoded in UTF-8
> >>> #75: FILE: contrib/libvhost-user/libvhost-user.c:9:
> >>> + * Marc-Andr Lureau <mlureau@redhat.com>
> >>> ^
> >>>
> >>> ERROR: Invalid UTF-8, patch and commit message should be encoded in UTF-8
> >>> #1579: FILE: contrib/libvhost-user/libvhost-user.h:8:
> >>> + * Marc-Andr Lureau <mlureau@redhat.com>
> >>> ^
> >>>
> >>> total: 2 errors, 0 warnings, 1950 lines checked
> >>
> >> Michael, could you check the encoding in that file and respin
> >> the patchset if necessary, please?
> >>
> >> thanks
> >> -- PMM
> >
> > I have no idea what this means.
>
> Look at the headers to patch 5/9:
>
> Subject: [PULL for-2.9 5/9] contrib: add libvhost-user
> Message-ID: <1481922841-4324-6-git-send-email-mst@redhat.com>
> References: <1481922841-4324-1-git-send-email-mst@redhat.com>
> MIME-Version: 1.0
> Content-Type: text/plain; charset=iso-8859-1
>
> Although that mail body says
> From: Marc-André Lureau <marcandre.lureau@redhat.com>
> it was doing so with the single-byte character from the iso-8859-1
> character set, instead of the multibyte UTF-8 character set.
>
> Compare that to another recent pull request from Gerd:
>
> Date: Wed, 4 Jan 2017 12:21:20 +0100
> Message-Id: <1483528883-1753-9-git-send-email-kraxel@redhat.com>
> In-Reply-To: <1483528883-1753-1-git-send-email-kraxel@redhat.com>
> References: <1483528883-1753-1-git-send-email-kraxel@redhat.com>
> MIME-Version: 1.0
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: quoted-printable
>
> where the mail body says:
> From: Marc-Andr=C3=A9 Lureau <marcandre.lureau@redhat.com>
>
> So somehow, your git settings differ from Gerd, in that your 'git
> send-email' (or however you are sending your pull request) is not
> picking the correct encoding. The buildbot is NOT seeing UTF-8, but
> ISO-8859-1 characters from your pull request, and is apparently unable
> to run iconv on the result before testing the patches out, resulting in
> the dropped bytes that are not already UTF-8 encoded. My mail reader,
> on the other hand, is smart enough to recognize both encodings, and my
> mail window sees the name correctly formatted in both mails, with no
> visual indication that the sources for the two mails were in different
> encodings. Which makes it a rather insidious problem to track down, if
> you don't spot the difference until dealing with some tool that isn't
> smart enough to do automatic conversion.
>
> But how to force git to send mail in UTF-8 is not something I've had to
> figure out (I'm relying on my distro's defaults) - you'll have to poke
> around your .git/config (or ~/.gitconfig) and see if you have some
> really old settings from an earlier time, or ask around on freenode's
> #git channel for better ideas.
>
> --
> Eric Blake eblake redhat com +1-919-301-3266
> Libvirt virtualization library http://libvirt.org
>
So the email might be malformed, but git commits are ok I think.
Peter, could you pls merge? I'll investigate my email settings later.
--
MST
next prev parent reply other threads:[~2017-01-06 21:20 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-16 21:15 [Qemu-devel] [PULL for-2.9 0/9] virtio, vhost, pc: fixes Michael S. Tsirkin
2016-12-16 21:15 ` [Qemu-devel] [PULL for-2.9 1/9] tests/vhost-user-bridge: remove false comment Michael S. Tsirkin
2016-12-16 21:15 ` [Qemu-devel] [PULL for-2.9 2/9] tests/vhost-user-bridge: remove unnecessary dispatcher_remove Michael S. Tsirkin
2016-12-16 21:16 ` [Qemu-devel] [PULL for-2.9 3/9] tests/vhost-user-bridge: indicate peer disconnected Michael S. Tsirkin
2016-12-16 21:16 ` [Qemu-devel] [PULL for-2.9 4/9] tests/vhost-user-bridge: do not accept more than one connection Michael S. Tsirkin
2016-12-16 21:16 ` [Qemu-devel] [PULL for-2.9 5/9] contrib: add libvhost-user Michael S. Tsirkin
2016-12-16 21:17 ` [Qemu-devel] [PULL for-2.9 6/9] tests/vhost-user-bridge: use contrib/libvhost-user Michael S. Tsirkin
2016-12-16 21:17 ` [Qemu-devel] [PULL for-2.9 7/9] i386: amd_iommu: fix MMIO register count and access Michael S. Tsirkin
2016-12-16 21:17 ` [Qemu-devel] [PULL for-2.9 8/9] pci: fix error message for express slots Michael S. Tsirkin
2016-12-16 21:17 ` [Qemu-devel] [PULL for-2.9 9/9] virtio: avoid using guest_notifier_mask in vhost-user mode Michael S. Tsirkin
2016-12-16 21:32 ` [Qemu-devel] [PULL for-2.9 0/9] virtio, vhost, pc: fixes no-reply
2016-12-17 11:18 ` Peter Maydell
2017-01-06 20:04 ` Michael S. Tsirkin
2017-01-06 20:38 ` Eric Blake
2017-01-06 20:42 ` Eric Blake
2017-01-06 21:20 ` Michael S. Tsirkin [this message]
2017-01-09 16:29 ` Peter Maydell
2017-01-09 16:48 ` Michael S. Tsirkin
2017-01-09 17:28 ` Peter Maydell
2017-01-10 1:34 ` Fam Zheng
2017-01-10 3:01 ` Michael S. Tsirkin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170106231922-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=eblake@redhat.com \
--cc=famz@redhat.com \
--cc=mlureau@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.