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

Re: GIT_CONFIG - what's the point?

From
Jeff King <peff@peff.net>
Date
Apr 1, 2016, 12:38 UTC
Message-ID
<20160401123830.GB12019@sigill.intra.peff.net>
In-Reply-To
<CAL20dLDQsti1qW7CrrEifPAhPp1snq9r5MgJL+mDwhLqhe6fyQ@mail.gmail.com>
On Thu, Mar 31, 2016 at 08:54:26PM -0400, Matthew Persico wrote:
> So, what's the point of GIT_CONFIG if only git-config uses it? Or did
> I miss a step?

There isn't a point to it. It's historical cruft that has been left in to avoid breaking older scripts. The same thing is generally better accomplished by using git-config's "--file" parameter. We should probably do a better job of making that clear in the documentation.

Or possibly deprecate it and eventually remove it entirely, as discussed in:

  http://thread.gmane.org/gmane.linux.debian.devel.bugs.general/1195694/focus=257770
-Peff
Previous: Christian CouderNext: Matthew Persico
Message 3 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.