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

Re: [PATCH] git-commit: filter out log message lines only when editor was run.

From
Junio C Hamano <junkio@cox.net>
Date
Jun 24, 2006, 00:21 UTC
Message-ID
<7vveqr769z.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<20060623220405.1915.28636.stgit@gandelf.nowhere.earth>
Yann Dirson <ydirson@altern.org> writes:
Show 5 quoted lines
> The current behaviour strips out lines starting with a # even when fed
> through stdin or -m.  This is particularly bad when importing history from
> another SCM (tailor 0.9.23 uses git-commit).  In the best cases all lines
> are stripped and the commit fails with a confusing "empty log message"
> error, but in many cases the commit is done, with loss of information.
I agree with this in principle but we would need to make sure
that our own scripts do not expect that the message is cleaned
up when feeding a commit log message via stdin, -m or -F, and if
they do fix them before applying this patch.
 
Previous: Yann Dirson
Message 2 of 2 in “git-commit: filter out log message lines only when editor was run.”
  1. git-commit: filter out log message lines only when editor was run.Yann Dirson, Jun 23, 2006
  2. Junio C HamanoJun 24, 2006

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.