Richard Purdie <rpurdie@xxxxxxxxx> 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. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html