Junio C Hamano <junkio@xxxxxxx> wrote: > Junio C Hamano <junkio@xxxxxxx> writes: > > > I am not quite sure how $GIT_CONFIG and $GIT_CONFIG_LOCAL were > > meant to be used. Are there any *real* users? With lack of > > Addendum. > > Judging from the way builtin-config.c::get_value() uses it, I > think whoever invented $GIT_CONFIG_LOCAL as a parallel to > $GIT_INDEX_FILE and $GIT_OBJECT_DIRECTORY, in other words, what > usually appear under $GIT_DIR can be placed somewhere completely > different. So I think the above "hack" I described still honors > its intended use. > > I am still not sure what good GIT_CONFIG would be to completely > override everything else, though. I just started using GIT_CONFIG in the experimental version of git-svn[1] which allows me to use .git/svn/config for tracking some metadata bits. I didn't want to pollute the users' .git/config with automatically read and state data in .git/config; so I started using .git/svn/config to avoid littering .git/svn/ with any tiny pieces of data I might need. -- Eric Wong [1] - git://bogomips.org/git-svn - 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