patch tracking issue

Simon Guinot simon at
Wed Jun 15 18:48:52 EST 2011

Hi Jeremy,

On Wed, Jun 15, 2011 at 09:44:56AM +0800, Jeremy Kerr wrote:
> Hi Simon,
> > Did you learn something from my patch email ? Any clue about this weird
> > behaviour ?
> Yes - sorry about the delay though.

No problems.

> It looks like the mail can't be decoded correctly. The content type of
> the patch part is:
>         Content-Type: text/plain
>         Content-Disposition: inline; filename=mutt-kw-1000-6693-519
>         Content-Transfer-Encoding: quoted-printable
> Since there is no encoding specified, patchwork assumes UTF-8.
> However, you have the following text in the patch:
>          Marius Gr=F6ger <mag at>
> \xf6 is not a valid UTF-8 sequence, so patchwork can't reliably
> represent the patch data. At the moment, that means that the parse
> fails.
> So - how was this mail generated?

The email was generated using git-format-patch and sent using
git-send-email. I think the patch is correct.

Actually, \xf6 is the iso-8859-{1,2,3,4} representation for 'ö' and
it is the way this character is encoded within the original source file.
Probably it should be fixed.

Thanks for your help :)

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <>

More information about the Patchwork mailing list