On Thu, 2006-06-08 at 06:30, Johannes Schindelin wrote: > > - The name. I personally prefer .gitconfig, since we talk about the repo > config all the time. But I have no strong feelings there. I like .gitconfig over .gitrc. > - The --no-local flag could be implemented more cleanly, but also less Could we have multiple levels, and have names that call out where it applies? Perhaps something like: --repo into $GIT_DIR/.gitconfig <- current default, right? --home into ~/.gitconfig --site into /etc/gitconfig --share into /usr/share/git/config My issue is that --no-local is vague and doesn't call out where it actually does go. There could be more than one different non-local place. > - With this, repo-config does no longer merit its name. What do people think > about making it a builtin named "git config"? (Of course, nothing hinders > us to keep the synonymous "repo-config" indefinitely...) I have often forgotten the "repo-" part, and go looking for the "git config ..." man page and command. I think it should be "git config". Perhaps, "git repo-config" would be "git config --repo ...." And "git config ..." would need an explict --home, --repo, --site type location flag from above? But, hey, that's all pre-coffee. jdl - : 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