Re: [PATCH 1/2] clone: respect the settings in $HOME/.gitconfig and /etc/gitconfig

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Daniel Barkalow <barkalow@xxxxxxxxxxxx> writes:

> 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@xxxxxxxxxxxx>

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.

--
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

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux