git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Patrick Rouleau <pfrouleau@gmail.com>
To: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Dec 2010, #01; Sat, 4)
Date: Sun, 5 Dec 2010 15:51:58 +0000 (UTC)	[thread overview]
Message-ID: <loom.20101205T162647-790@post.gmane.org> (raw)
In-Reply-To: alpine.SOC.2.00.1012051420230.18993@kekkonen.cs.hut.fi

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

> 
> 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?

  reply	other threads:[~2010-12-05 15:52 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-05  6:30 What's cooking in git.git (Dec 2010, #01; Sat, 4) Junio C Hamano
2010-12-05  7:39 ` Jeff King
2010-12-05 19:54   ` Junio C Hamano
2010-12-06  0:54     ` aleksi.aalto
2010-12-09 17:27     ` Jeff King
2010-12-10 19:55       ` Junio C Hamano
2010-12-05 10:13 ` Yann Dirson
2010-12-05 20:23   ` Junio C Hamano
2010-12-06  7:29     ` Yann Dirson
2010-12-06  8:13       ` Miles Bader
2010-12-06  8:21         ` Yann Dirson
2010-12-06  8:39           ` Miles Bader
2010-12-06  8:48             ` Yann Dirson
2010-12-06  9:13               ` Miles Bader
2010-12-06 11:31                 ` Yann Dirson
2010-12-06 11:37                 ` Matthieu Moy
2010-12-10 21:59                 ` Junio C Hamano
2010-12-05 12:36 ` aleksi.aalto
2010-12-05 15:51   ` Patrick Rouleau [this message]
2010-12-05 13:00 ` Erik Faye-Lund
2010-12-05 20:15   ` Junio C Hamano
2010-12-05 15:00 ` Michael J Gruber
2010-12-05 20:06   ` Junio C Hamano
2010-12-06  8:55     ` Michael J Gruber
2010-12-06 15:39       ` Thiago Farina
2010-12-08 11:23 ` t9010 broken in pu [Re: What's cooking in git.git (Dec 2010, #01; Sat, 4)] Thomas Rast
2010-12-08 11:28   ` Jonathan Nieder

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=loom.20101205T162647-790@post.gmane.org \
    --to=pfrouleau@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).