git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Jan Krüger <jk@jk.gs>
Date
Dec 3, 2010, 12:59 UTC
Message-ID
<20101203135944.31d7cfbf@jk.gs>
In-Reply-To
<4CF8D243.50108@gmx.com>
--- Martin Krüger <martin.krueger@gmx.com> wrote:
Show 8 quoted lines
> Consider this log-Message:
> commit ea2cd63dfe9b3ac3581b6cff8b13a52e69066242
> Author: martin <martin@chad.upnx.de>
> 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.

Show 9 quoted lines
> [...]
> 
> 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
How is that correct? It's different from the original commit message.
-Jan
Previous: Martin KrügerNext: Michael J Gruber
Message 2 of 4 in “Problem in Patches with commit-messages containing non-ascii”
  1. Martin KrügerDec 3, 2010
  2. Jan KrügerDec 3, 2010
  3. Michael J GruberDec 3, 2010
  4. Andreas SchwabDec 3, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.