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

Overlong lines with git-merge --log

From
Tim Janik <timj@gnu.org>
Date
Nov 2, 2012, 01:30 UTC
Message-ID
<50932227.3090401@gnu.org>
Hey all.

Using git-merge --log to merge commit messages that spawn multiple lines will produce overlong summary lines. That's because each summary line for a commit includes the entire commit message (all lines concatenated).

According to git-fmt-merge-msg(1), --log should 'populate the log message with one-line descriptions' instead of using the entire commit messages. Which would make a lot of sense, it's just not working as advertised.

Encountered with git version 1.7.9.5.
-- 
Yours sincerely,
Tim Janik

---
http://timj.testbit.eu/ - Free software Author
Next: Jeff King
Message 1 of 4 in “Overlong lines with git-merge --log”
  1. Tim JanikNov 2, 2012
  2. Jeff KingNov 2, 2012
  3. Tim JanikNov 2, 2012
  4. Stephen BashNov 2, 2012

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.