From: Junio C Hamano <gitster@pobox.com>
Date: Wed, 01 Dec 2010 22:06:27 GMT
Subject: Re: [PATCH] status: show branchname with a configurable color
Message-ID: <7vlj49tafw.fsf@alter.siamese.dyndns.org>
In-Reply-To: <1290037205-19470-1-git-send-email-aga@iki.fi>

aga@iki.fi writes:

>  color.status.<slot>::
> -	Use customized color for status colorization. `<slot>` is
> -	one of `header` (the header text of the status message),
> -	`added` or `updated` (files which are added but not committed),
> -	`changed` (files which are changed but not added in the index),
> -	`untracked` (files which are not tracked by git), or
> -	`nobranch` (the color the 'no branch' warning is shown in, defaulting
> -	to red). The values of these variables may be specified as in
> -	color.branch.<slot>.
> +	Use customized color for status colorization. `<slot>` is one of
> +	`header` (the header text of the status message), `added` or `updated`
> +	(files which are added but not committed), `changed` (files which
> +	are changed but not added in the index), `untracked` (files which
> +	are not tracked by git), `branch` (the current branch) or `nobranch`
> +	(the color the 'no branch' warning is shown in, defaulting to red). The
> +	values of these variables may be specified as in color.branch.<slot>.

Yuck.  Why did you have to re-wrap the paragraph to make diff unreadable?

It also is customary to make the default plain, so that existing users
won't suddenly get a new and funky behaviour.

I'll queue with a slight rearrangement.

Thanks.