The environment variables GIT_CONFIG_NOGLOBAL and GIT_CONFIG_NOSYSTEM which have the opposite effect of the --global and --system switches to git-config are completely undocumented. This mentions them in the 'files' and 'environment' sections of the manpage for git-config where GIT_CONFIG is already mentioned. Signed-off-by: Jan KrÃger <jk@xxxxx> --- Documentation/git-config.txt | 10 ++++++++++ 1 files changed, 10 insertions(+), 0 deletions(-) diff --git a/Documentation/git-config.txt b/Documentation/git-config.txt index 543dd64..c3ea29c 100644 --- a/Documentation/git-config.txt +++ b/Documentation/git-config.txt @@ -210,6 +210,9 @@ variables. The '--global' and the '--system' options will limit the file used to the global or system-wide file respectively. The GIT_CONFIG environment variable has a similar effect, but you can specify any filename you want. +You can also set the environment GIT_CONFIG_NOGLOBAL and GIT_CONFIG_NOSYSTEM +to explicitly prevent git from falling back to global/system settings. + ENVIRONMENT ----------- @@ -219,6 +222,14 @@ GIT_CONFIG:: Using the "--global" option forces this to ~/.gitconfig. Using the "--system" option forces this to $(prefix)/etc/gitconfig. +GIT_CONFIG_NOGLOBAL:: + If set to true, do not use the global configuration file + in ~/.gitconfig. + +GIT_CONFIG_NOSYSTEM:: + If set to true, do not use the system-wide configuration file in + /etc/gitconfig. + See also <<FILES>>. -- 1.7.2.3.392.g02377.dirty -- 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