Re: [PATCH v3 1/3] builtin/config: introduce `--default`

From: Taylor Blau <me@ttaylorr.com>
Date: Apr 5, 2018, 02:45 UTC
Message-ID: <20180405024519.GA31883@syl.local>
In-Reply-To: <xmqqy3i930bl.fsf@gitster-ct.c.googlers.com>

On Fri, Mar 30, 2018 at 11:06:22AM -0700, Junio C Hamano wrote:

Show 14 quoted lines

> Taylor Blau <me@ttaylorr.com> writes:
>
> > For some use cases, callers of the `git-config(1)` builtin would like to
> > fallback to default values when the slot asked for does not exist. In
> > addition, users would like to use existing type specifiers to ensure
> > that values are parsed correctly when they do exist in the
> > configuration.
> > ...
> > +--default value::
> > +  When using `--get`, and the requested slot is not found, behave as if value
> > +  were the value assigned to the that slot.
>
> For "diff.<slot>.color", the above is OK, but in general,
> configuration variables are not called "slot".  s/slot/variable/.

Thanks; I was unaware of this convention. I have changed "slot" to "variable" as you suggested in the subsequent re-roll.

Thanks, Taylor