threads / discuss / 52545

Reduction in blanks in `git status` makes output pretty cramped

Subject: Reduction in blanks in `git status` makes output pretty cramped

## tl;dr

3 messages between Dec 31, 2019 and Jan 6, 2020.

replies: 2people: 2as markdown or json

Anthony Sottile· Dec 31, 2019, 23:18 UTC · lore

This is a comment on 7b098429355bb3271f9ffdf73b97f2ef82794fea

https://github.com/git/git/commit/7b098429355bb3271f9ffdf73b97f2ef82794fea

Jeff King· Jan 6, 2020, 21:23 UTC · re: Anthony Sottile · lore

Re: Reduction in blanks in `git status` makes output pretty cramped

On Tue, Dec 31, 2019 at 03:18:17PM -0800, Anthony Sottile wrote:

> This is a comment on 7b098429355bb3271f9ffdf73b97f2ef82794fea
> 
> https://github.com/git/git/commit/7b098429355bb3271f9ffdf73b97f2ef82794fea

I don't have much of an opinion myself (I didn't even notice, as I think it only affects the case where advice.statusHints is enabled). But there's more discussion in this thread:

  https://lore.kernel.org/git/20190430060210.79610-1-johnlinp@gmail.com/

about whether to add or remove blank lines. ;)

+cc people who expressed opinions there

Anthony Sottile· Jan 6, 2020, 23:06 UTC · re: Jeff King · lore

Re: Reduction in blanks in `git status` makes output pretty cramped

> (I didn't even notice, as I think it only affects the case where advice.statusHints is enabled

yeah this makes sense -- (unfortunately) advice.statusHints appears to be the default

Anthony