Re: What's cooking in git.git (Dec 2010, #01; Sat, 4)

From: Patrick Rouleau <pfrouleau@gmail.com>
Date: Dec 5, 2010, 15:51 UTC
Message-ID: <loom.20101205T162647-790@post.gmane.org>
In-Reply-To: <alpine.SOC.2.00.1012051420230.18993@kekkonen.cs.hut.fi>

 <aleksi.aalto <at> iki.fi> writes:

Show 15 quoted lines

> 
> On Sat, 4 Dec 2010, Junio C Hamano wrote:
> > * aa/status-hilite-branch (2010-11-18) 1 commit
> > - status: show branchname with a configurable color
> >
> > I am indifferent/uninterested; I don't see anything wrong with it, but I
> > do not find coloring the field particularly useful myself.
> 
> The idea for this patch came from my daywork, where I have lately been 
> trying to teach new users effective use of Git. We promote heavy usage of 
> "git status" for new users in order for them to understand what all the 
> basic commands do. A great amount of users fail to notice in which branch 
> they are even when looking at the status message. I think this small tweak 
> could help at least some of such new users without causing considerable 
> harm for more advanced users.

I see the same problem at my daywork.

But like others, I'm not sure about the default color. I would opt for green which is the default used by the branch command for highlight the current branch.

Maybe we can add an empty line after the branch name, to make it stand out a bit more, with or without color?