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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Martin KrÃger <martin.krueger@xxxxxxx> writes:

> Then git generates this patch:
>
> From ea2cd63dfe9b3ac3581b6cff8b13a52e69066242 Mon Sep 17 00:00:00 2001
> From: martin <martin@xxxxxxxxxxxx>
> 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@xxxxxxxxxxxx>
> 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@xxxxxxxxxxxxxx
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]