Hi, On Sun, 11 Feb 2007, Marco Costalba wrote: > On 2/11/07, Johannes Schindelin <Johannes.Schindelin@xxxxxx> wrote: > > > > > So I am certain that you made a mistake when you need to ignore the > > settings in $HOME/.gitconfig. > > > > Please do the following: > > $ cd <git tree repo> > $ git repo-config --global --unset user.name > $ git repo-config --unset user.name > $ git gui > > Then go to Edit->options, you will see empty both 'git repository' and > 'Global (All repositories)' > > Then exit 'git gui' and type: > > $ git repo-config --global user.name dummy > $ git gui > > Then go to Edit->options and.... surprise! dummy has been added to > both panes instead of only in 'Global' one. I don't know. If you want that level of control, yes. But as has been suggested before: .git/config as well as ~/.gitconfig have been meant to be edited manually, but some people really need a special purpose UI for everything, don't they? As I said, for this you should use "GIT_CONFIG=$GIT_DIR/config git config". > The bug is not in 'git gui' but in 'git repo-config' that when queried > for user.name if doesn't find it in local config, silently falls back > in global config. This is not documented and probably a bug because > documentation of --global option says: > > --global:: > Use global ~/.gitconfig file *rather than* the repository .git/config. Yes, this is probably a bug. But it's obvious that if git-config _without_ --global would _not_ use ~/.gitconfig, that would rather make ~/.gitconfig pointless, wouldn't it? So yes, the description should mention that this is meant for the case of _setting_ variables, not _querying_ variables. The original poster (Sean) probaly though -- IMHO correctly -- that querying with --global makes no sense. Ciao, Dscho - 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