git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 6, 2020, 18:01 UTC
Message-ID
<xmqq4ktwwl1g.fsf@gitster.c.googlers.com>
In-Reply-To
<20200406130524.GA1276@coredump.intra.peff.net>
Jeff King <peff@peff.net> writes:
Show 33 quoted lines
> On Mon, Apr 06, 2020 at 10:48:06AM +0200, Tomáš Procházka wrote:
>
>> [includeIf "gitdir:~/Workspace/Showmax/"]
>>    path = ~/Workspace/Showmax/.gitconfig
>> [...]
>> I get correct email setting if I run command without `--global` flag.
>> But What I understand from the [`git-config`
>> docs](https://git-scm.com/docs/git-config#_description) if no flag is
>> passed the values are read from system, global and local.
>
> Right, I'd expect that to work, but...
>
>> If I run commands one by one, No returns the ~correct~ expected email:
>> 
>> ~ $ git -C <pwd/to/showmax/project> config --system user.email
>> ~ $ git -C <pwd/to/showmax/project> config --global user.email
>> tomas.prochazka5d@gmail.com
>> ~ $ git -C <pwd/to/showmax/project> config --local user.email
>
> 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)?

Previous: Jeff KingNext: Jeff King
Message 3 of 4 in “Fwd: Q: use '-C' flag with 'git config --global'”
  1. Tomáš ProcházkaApr 6, 2020
  2. Jeff KingApr 6, 2020
  3. Junio C HamanoApr 6, 2020
  4. Jeff KingApr 6, 2020

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.