Re: [PATCH 1/2] clone: respect the settings in $HOME/.gitconfig and /etc/gitconfig
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Jun 29, 2008, 20:36 UTC
- Message-ID
- <7vprq07zco.fsf@gitster.siamese.dyndns.org>
- In-Reply-To
- <alpine.LNX.1.00.0806291359330.19665@iabervon.org>
Daniel Barkalow <barkalow@iabervon.org> writes:
Show 9 quoted lines
> There's no need to use the environment variable to direct the generation > of the config file in the C version of clone, and having it not defined > means that global and per-user configuration is available. This is > necessary for the fetching portion, and could be useful someday for the > init portion as well. It is unlikely that the user would want the > repository's configuration in some non-default location, but no less > likely than with any other git command besides "git config". > > Signed-off-by: Daniel Barkalow <barkalow@iabervon.org>
Thanks, will queue together with the earlier [2/2] from Dscho.
Can we have updates to the testsuite as well? We would probably have to fudge $HOME and have some entries in $HOME/.gitconfig to simulate the situation that triggered the original discussion.