* Jeff King <peff@xxxxxxxx> [080501 00:00]: > On Fri, May 02, 2008 at 12:34:10PM +0200, Wincent Colaiuta wrote: > > > But evidently given that there has been so much backlash against the > > patch the only way to keep everyone happy will be to make this > > configurable. > > Agreed. > > But I wonder why there seems to be such a split between people who > clearly have short git-status output, and those who have long git-status > output. > > I keep my "untracked files" list tidy. IOW, I always get: > > $ git status > # On branch master > nothing to commit (working directory clean) > > and if I don't, then I should be taking some action to commit things, > clean them up, or add them to my .git/info/exclude file. Do other people > generally carry around a lot of cruft that "git status" reports? I like the change. I don't usually have long git status output; I manage my .gitignore and $GITDIR/info/exclude religously. But in those cases, the pager has no affect (LESS=FRSX), so it doesn't bother me. But sometime I have done something which affects a lot of files. Either on purpose, or by accident, and suddenly git status has lots of output. And I'm usually not thinking git status will have reams of output and at that time, I really like *not* having to re-run the command with -p or | $PAGER. a. -- Aidan Van Dyk Create like a god, aidan@xxxxxxxxxxx command like a king, http://www.highrise.ca/ work like a slave.
Attachment:
signature.asc
Description: Digital signature
