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

Re: Overlong lines with git-merge --log

From
Tim Janik <timj@gnu.org>
Date
Nov 2, 2012, 13:24 UTC
Message-ID
<5093C98D.90807@gnu.org>
In-Reply-To
<20121102100519.GC30221@sigill.intra.peff.net>
On 02.11.2012 11:05, Jeff King wrote:
> Taking just the first line of those often cuts off the useful part. It
> was deemed less bad to show the whole message as a subject rather than
> cut it off arbitrarily.

Thanks a lot for the explanation, I'm using git directly here, but the two cases I had indeed lacked this newline.

-- 
Yours sincerely,
Tim Janik

---
http://timj.testbit.eu/ - Free software Author
Previous: Jeff KingNext: Stephen Bash
Message 3 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.