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

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

 



Jan KrÃger venit, vidit, dixit 03.12.2010 13:59:
> --- Martin KrÃger <martin.krueger@xxxxxxx> wrote:
> 
>> Consider this log-Message:
>> commit ea2cd63dfe9b3ac3581b6cff8b13a52e69066242
>> Author: martin <martin@xxxxxxxxxxxx>
>> Date:   Fri Nov 19 18:58:58 2010 +0100
>>
>>     Methoden Ãberall angepasst.
>>     Ausser Aussnahmen
>>
> 
> FWIW, support for multi-line summaries is very limited. Several
> tools assume that the log message has this format:
> 
> <Summary in one line>
> <Blank line>
> <Details>
> 
> So one could argue that your patch fixes something that isn't really
> supported anyway.
> 
>> [...]
>>
>> 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
> 
> How is that correct? It's different from the original commit message.
> 
> -Jan

Also, it is "AuÃer Ausnahmen" even after the latest spelling reform ;)

Michael
--
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]