Re: [PATCH 1/2] clone: respect the settings in $HOME/.gitconfig and /etc/gitconfig
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Jun 30, 2008, 06:25 UTC
- Message-ID
- <7vskuv30e6.fsf@gitster.siamese.dyndns.org>
- In-Reply-To
- <7vwsk730mm.fsf@gitster.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> writes:
Show 8 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. > > I think ignoring end-user GIT_CONFIG like this patch does, instead of > doing random nonsense, would be a good bugfix for "git clone".
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.