Re: git-status too verbose?

From: Andreas Ericsson <ae@op5.se>
Date: Mar 7, 2006, 09:19 UTC
Message-ID: <440D503E.8090007@op5.se>
In-Reply-To: <7vacc36r4v.fsf@assigned-by-dhcp.cox.net>

Junio C Hamano wrote:

Show 5 quoted lines

> 
> Why do people think mysterious single letter abbreviation is
> better than spelled out words in an output meant for human
> consumption?
>

Familiarity, I suspect.

Show 15 quoted lines

> 
> I agree that it would be useful if we had a tool that showed the
> two status that matter for each file, grouped together on one
> line, e.g.
> 
> 			HEAD->index	index->files
> 	------------------------------------------------
> 	hello.c		unmodified      modified
>         world.c		modified	unmodified
> 	frotz.c		new		unmodified
>         ...
> 	garbage.c~	???		n/a
> 
> for the current index file and the current HEAD commit.
>

Could we have 'same' or some such instead of 'unmodified'? It's a bit close to 'modified' for the eye to find it quickly.

Show 6 quoted lines

> You obviously need to learn how to read it though.  The first
> column means what you _would_ commit if you just said "git
> commit" without doing anything else now; the second column is
> what you _could_ commit if you did some update-index and then
> said "git commit" (or ran "git commit" with paths arguments).
>

Pretty-printing will be easier if the filename is last, and it will look a lot neater if all columns are aligned.

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231