Re: Problem in Patches with commit-messages containing non-ascii

From: Andreas Schwab <schwab@linux-m68k.org>
Date: Dec 3, 2010, 19:03 UTC
Message-ID: <m2r5dyd6h1.fsf@igel.home>
In-Reply-To: <4CF8D243.50108@gmx.com>

Martin Krüger <martin.krueger@gmx.com> writes:

Show 18 quoted lines

> Then git generates this patch:
>
> From ea2cd63dfe9b3ac3581b6cff8b13a52e69066242 Mon Sep 17 00:00:00 2001
> From: martin <martin@chad.upnx.de>
> Date: Fri, 19 Nov 2010 18:58:58 +0100
> Subject: [PATCH] =?UTF-8?q?Methoden=20=C3=BCberall=20angepasst.?=
>  =?UTF-8?q?Ausser=20Aussnahmen?=
> MIME-Version: 1.0
> Content-Type: text/plain; charset=UTF-8
> Content-Transfer-Encoding: 8bit
>
> Applyin leads to a correct commit-Messsage:
>
> commit 62d06e3415ec0726dbd58c11ed93771502b77805
> Author: martin <martin@chad.upnx.de>
> Date:   Fri Nov 19 18:58:58 2010 +0100
>
>     Methoden überall angepasst.Ausser Aussnahmen

That's at least missing a space after the period.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."