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

Re: [PATCH 2/2] diff: color statistics (stat, shortstat, numstat)

From
Markus Heidelberg <markus.heidelberg@web.de>
Date
Apr 25, 2009, 11:09 UTC
Message-ID
<200904251309.39816.markus.heidelberg@web.de>
In-Reply-To
<7vbpqlac6n.fsf@gitster.siamese.dyndns.org>
Junio C Hamano, 25.04.2009:
Show 10 quoted lines
> Markus Heidelberg <markus.heidelberg@web.de> writes:
> 
> > stat/shortstat:
> > Color added and removed lines and the corresponding signs ('+' and '-')
> > in the summary.
> >
> > numstat:
> > Color added and removed lines per file.
> 
> I find this extremely unreadable.

I know one can overdo it with colors, but I don't think it's the case for the stat/shortstat summary line here. Of course this is very subjective and if the consensus is not to have colors there, then it's OK.

> Also numstat being for porcelain use, I
> do not see the point.

It gives you an information that --stat doesn't give you: the exact count of added and removed lines per file. Also for long path names you don't have to bother with --stat=x,y

Having said this, I have to admit that I didn't use it myself up to now.
> I think [1/2] that removes the (plain)coloring of the stat summary text is
> Ok.

Do you mean the whole patch 1/2 is OK or only the summary part and the filenames should stay with plain coloring? I think the former.

> The code is painting the stat summary in the same color as the
> filenames in the stat graph, and the default "plain" color happens to be
> "do not color--just use the terminal default", so it probably does not
> have any practical difference.
Eh, yes, for people setting color.diff.plain
Previous: Junio C Hamano
Message 6 of 6 in “text in --stat is colored like color.diff.plain”
  1. Markus HeidelbergApr 22, 2009
  2. 1/2 diff: do not color --stat output like patch contextMarkus Heidelberg, Apr 24, 2009
  3. 2/2 diff: color statistics (stat, shortstat, numstat)Markus Heidelberg, Apr 24, 2009
  4. Jeff KingApr 24, 2009
  5. Junio C HamanoApr 24, 2009
  6. Markus HeidelbergApr 25, 2009

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.