From: "Jan Krüger" <jk@jk.gs>
To: Git ML <git@vger.kernel.org>
Subject: [PATCH] Documentation: mention environment variables GIT_CONFIG_NO(GLOBAL|SYSTEM)
Date: Sun, 3 Oct 2010 23:53:29 +0200 [thread overview]
Message-ID: <20101003235329.6f4d2572@jk.gs> (raw)
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@jk.gs>
---
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
next reply other threads:[~2010-10-03 21:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-03 21:53 Jan Krüger [this message]
2010-10-03 23:10 ` [PATCH] Documentation: mention environment variables GIT_CONFIG_NO(GLOBAL|SYSTEM) Sverre Rabbelier
2010-10-03 23:27 ` Junio C Hamano
2010-10-04 6:31 ` Jan Krüger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101003235329.6f4d2572@jk.gs \
--to=jk@jk.gs \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).