Re: [PATCH 1/2] clone: respect the settings in $HOME/.gitconfig and /etc/gitconfig
- From
Jeff King <peff@peff.net>
- Date
- Jun 30, 2008, 06:40 UTC
- Message-ID
- <20080630064031.GA30600@sigill.intra.peff.net>
- In-Reply-To
- <7vskuv30e6.fsf@gitster.siamese.dyndns.org>
On Sun, Jun 29, 2008 at 11:25:05PM -0700, Junio C Hamano wrote:
Show 5 quoted lines
> > Honestly, GIT_CONFIG is purely for scripts like git-svn that muck with > > files that are in the config format to have a way to make sure that they > > access the file they intend to, and being able to use GIT_CONFIG to keep > > git programs from reading from $HOME/.gitconfig is primarily for giving > > our test scripts repeatable environment, nothing more.
[...]
> Of course, that would have downsides as well. Now git-clone tests cannot > be sanely written without setting $HOME to somewhere stable; otherwise > they can be randomly affected by buggy $HOME/.gitconfig files the end user > may have.
I thought we went through all of this before, and it led to 8bfa6bd6. The test scripts set GIT_CONFIG_NOSYSTEM and GIT_CONFIG_NOGLOBAL to achieve the same suppression effect.
-Peff