From: Junio C Hamano <gitster@pobox.com>
Date: Fri, 12 Aug 2011 19:16:44 GMT
Subject: Re: Overriding ~/.gitconfig using GIT_CONFIG
Message-ID: <7vr54qmodf.fsf@alter.siamese.dyndns.org>
In-Reply-To: <1313163498.14274.505.camel@rex>

Richard Purdie <rpurdie@rpsys.net> writes:

> Looking through the manuals/code, it suggests I should be able to do:
>
> GIT_CONFIG=/dev/null git XXX
>
> and all should work happily. It doesn't though. As an example, with a
> ~/.gitconfig, "GIT_CONFIG=/dev/null git fetch --all" is clearly
> accessing the file in ~ and then acting upon it.

If the manual says the above is expected for any value of XXX, then that
is a bug in the manual since mid 2008, I think.

See dc87183 (Only use GIT_CONFIG in "git config", not other programs,
2008-06-30).

I _think_ these days a workaround to force a known config is to set HOME
to a value that has a known .gitconfig (or no such file), and decline
usage of /etc/git.config by exporting GIT_CONFIG_NOSYSTEM.