doc: advertise GIT_CONFIG_NOSYSTEM
On a multiuser system where mortals do not have write access to /etc, the GIT_CONFIG_NOSYSTEM variable is the best tool we have to keep getting work done when a syntax error or other problem renders /etc/gitconfig buggy, until the sysadmin sorts the problem out. Noticed while experimenting with teaching git to error out when /etc/gitconfig is unreadable. Signed-off-by: Jonathan Nieder <jrnieder@gmail.com> Acked-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Jonathan Nieder committed
Oct 14, 2012 at 01:53 UTC
e8ef401cd0ff5d51b148c1b1297dab6ef32227c1
2 files changed
+12
Documentation/git-config.txt
+4
@@ -240,6 +240,10 @@ GIT_CONFIG::
240
Using the "--global" option forces this to ~/.gitconfig. Using the
241
"--system" option forces this to $(prefix)/etc/gitconfig.
242
243
+GIT_CONFIG_NOSYSTEM::
244
+ Whether to skip reading settings from the system-wide
245
+ $(prefix)/etc/gitconfig file. See linkgit:git[1] for details.
246
+
247
See also <<FILES>>.
248
249
Documentation/git.txt
+8
@@ -771,6 +771,14 @@ for further details.
771
and read the password from its STDOUT. See also the 'core.askpass'
772
option in linkgit:git-config[1].
773
774
+'GIT_CONFIG_NOSYSTEM'::
775
+ Whether to skip reading settings from the system-wide
776
+ `$(prefix)/etc/gitconfig` file. This environment variable can
777
+ be used along with `$HOME` and `$XDG_CONFIG_HOME` to create a
778
+ predictable environment for a picky script, or you can set it
779
+ temporarily to avoid using a buggy `/etc/gitconfig` file while
780
+ waiting for someone with sufficient permissions to fix it.
781
+
782
'GIT_FLUSH'::
783
If this environment variable is set to "1", then commands such
784
as 'git blame' (in incremental mode), 'git rev-list', 'git log',