From: Junio C Hamano <gitster@pobox.com>
Date: Fri, 30 Mar 2018 18:09:43 GMT
Subject: Re: [PATCH v3 3/3] builtin/config: introduce `color` type specifier
Message-ID: <xmqqtvsx3060.fsf@gitster-ct.c.googlers.com>
In-Reply-To: <20180329011634.68582-4-me@ttaylorr.com>

Taylor Blau <me@ttaylorr.com> writes:

> @@ -184,6 +183,7 @@ Valid `[type]`'s include:
>  --bool-or-int::
>  --path::
>  --expiry-date::
> +--color::
>    Historical options for selecting a type specifier. Prefer instead `--type`,
>    (see: above).
>  
> @@ -223,6 +223,9 @@ Valid `[type]`'s include:
>  	output it as the ANSI color escape sequence to the standard
>  	output.  The optional `default` parameter is used instead, if
>  	there is no color configured for `name`.
> ++
> +It is preferred to use `--type=color`, or `--type=color --default=[default]`
> +instead of `--get-color`.

Wasn't the whole point of the preliminary --type=<type> patch to
avoid having to add thse two hunks?