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

Re: Overlong lines with git-merge --log

From
SBStephen Bash <bash@genarts.com>
Date
Nov 2, 2012, 13:49 UTC
Message-ID
<982632649.556351.1351864173516.JavaMail.root@genarts.com>
In-Reply-To
<5093C98D.90807@gnu.org>
----- Original Message -----
Show 12 quoted lines
> From: "Tim Janik" <timj@gnu.org>
> Sent: Friday, November 2, 2012 9:24:29 AM
> Subject: Re: Overlong lines with git-merge --log
> 
> 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.
FWIW we use merge --log quite extensively here at the office, and I've developed a habit to skim the extremely long lines and attempt to cut them intelligently (something I don't trust the computer to do for me).  Sometimes that means taking the second or third sentence if it's a better summary, sometimes it's just abbreviating the first.  Now that merge automatically spawns an editor, this is quite convenient (though it does take a bit longer).

Thanks, Stephen

Previous: Tim Janik
Message 4 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.