Re: activate color.ui by default (Re: What's cooking in git.git (May 2013, #05; Mon, 20))

From: Junio C Hamano <gitster@pobox.com>
Date: May 21, 2013, 15:52 UTC
Message-ID: <7vli78qqi6.fsf@alter.siamese.dyndns.org>
In-Reply-To: <vpqd2skzh9c.fsf@grenoble-inp.fr>

Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> writes:

Show 21 quoted lines

> Junio C Hamano <gitster@pobox.com> writes:
>
>> * mm/color-auto-default (2013-05-15) 2 commits
>>  - make color.ui default to 'auto'
>>  - config: refactor management of color.ui's default value
>>
>>  Flip the default for color.ui to 'auto', which is what many
>>  tutorials recommend new users to do.
>>
>>  I think this is ready for 'next', but we may want to audit tutorials
>>  to see if we need to adjust them if they suggest to set color.ui as
>>  the first thing to do when they meet Git.
>
> The little grepping I did in our docs didn't show much about color.ui,
> and nothing about its default value (just technical documentation, not
> beginner-oriented).
>
> Other than that, the patch makes the doc say "... `auto` (this is the
> default since Git 2.0)". I'm slightly in favor of delaying the change
> until Git 2.0 and keeping it as-is, but I'm OK with letting it in the
> next minor version if other people think it should

I do not have a strong opinion on this either, but slightly in favor of saying 2.0 is for changes that are more important than this kind of thing so we balance out ;-)

> (I did not see strong
> opinion on that, but I think the general opinion from the discussion was
> it would be OK). If so, I can resend without the 2.0 mention (or Junio
> can edit it locally).