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

GIT_CONFIG - what's the point?

From
Matthew Persico <matthew.persico@gmail.com>
Date
Apr 1, 2016, 00:54 UTC
Message-ID
<CAL20dLDQsti1qW7CrrEifPAhPp1snq9r5MgJL+mDwhLqhe6fyQ@mail.gmail.com>
Greetings.

Given the GIT_CONFIG environment variable can change 'git config' behaves, it stands to reason that if GIT_CONFIG is defined, then ALL git commands obey the value of GIT_CONFIG and use that file for config info.

As a test, exported GIT_CONFIG=/tmp/ohm, copied ~/.gitconfig to /tmp/ohm, moved ~/.gitconfig to ~/.gitconfig.hold and then tried git st, where 'st' is an alias for status in my config file.

No dice. git st was unrecognized.

So, what's the point of GIT_CONFIG if only git-config uses it? Or did I miss a step?

Thanks
-- 
Matthew O. Persico
Next: Christian Couder
Message 1 of 7 in “GIT_CONFIG - what's the point?”
  1. Matthew PersicoApr 1, 2016
  2. Christian CouderApr 1, 2016
  3. Jeff KingApr 1, 2016
  4. Matthew PersicoApr 1, 2016
  5. Jeff KingApr 1, 2016
  6. SZEDER GáborApr 1, 2016
  7. Matthew PersicoApr 3, 2016

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.