All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
Cc: git@vger.kernel.org
Subject: Re: activate color.ui by default (Re: What's cooking in git.git (May 2013, #05; Mon, 20))
Date: Tue, 21 May 2013 08:52:49 -0700	[thread overview]
Message-ID: <7vli78qqi6.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <vpqd2skzh9c.fsf@grenoble-inp.fr> (Matthieu Moy's message of "Tue, 21 May 2013 13:47:43 +0200")

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

> 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).

  reply	other threads:[~2013-05-21 15:52 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-21  0:15 What's cooking in git.git (May 2013, #05; Mon, 20) Junio C Hamano
2013-05-21  0:22 ` Felipe Contreras
2013-05-21  1:16 ` Johan Herland
2013-05-21 15:35   ` Junio C Hamano
2013-05-22  7:49     ` Johan Herland
2013-07-01 21:56       ` Junio C Hamano
2013-07-02 13:02         ` Johan Herland
2013-05-21  7:19 ` Thomas Rast
2013-05-21 15:36   ` Junio C Hamano
2013-05-29  5:19   ` Jeff King
2013-05-21 11:47 ` activate color.ui by default (Re: What's cooking in git.git (May 2013, #05; Mon, 20)) Matthieu Moy
2013-05-21 15:52   ` Junio C Hamano [this message]
2013-05-22  7:30 ` What's cooking in git.git (May 2013, #05; Mon, 20) Michael J Gruber
2013-05-22  7:36   ` Michael J Gruber
2013-05-22 16:36   ` Junio C Hamano
2013-05-23 10:07     ` Michael J Gruber
2013-05-23 14:40       ` Junio C Hamano
2013-05-23 15:31         ` Michael J Gruber
2013-05-23 17:37           ` Junio C Hamano

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

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

  git send-email \
    --in-reply-to=7vli78qqi6.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=Matthieu.Moy@grenoble-inp.fr \
    --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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.