Re: Fwd: Q: use '-C' flag with 'git config --global'

From: Jeff King <peff@peff.net>
Date: Apr 6, 2020, 18:05 UTC
Message-ID: <20200406180508.GA23427@coredump.intra.peff.net>
In-Reply-To: <xmqq4ktwwl1g.fsf@gitster.c.googlers.com>

On Mon, Apr 06, 2020 at 11:01:31AM -0700, Junio C Hamano wrote:

Show 17 quoted lines

> > There's another difference when asking to read from a specific file:
> > includes are not turned on by default. Try
> >
> >   git -C ... config --global --includes user.email
> >
> > This is covered briefly in git-config(1):
> >
> >   --[no-]includes
> >     Respect include.* directives in config files when looking up values.
> >     Defaults to off when a specific file is given (e.g., using --file,
> >     --global, etc) and on when searching all config files.
> >
> > This can be confusing, but was necessary to keep compatibility with
> > scripted manipulations of those files when includes were introduced.
> 
> So, in short, the mention of -C in the report was red herring and it
> was all about --(system|global|local)?

Yes. It's relevant insofar as being in the repo to trigger the conditional include, but "cd" would also have sufficed for that. :)

-Peff