When a syntax error or other problem renders /etc/gitconfig buggy 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 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 <jrnie...@gmail.com>
 Documentation/git-config.txt | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/Documentation/git-config.txt b/Documentation/git-config.txt
index eaea0791..907a1fd5 100644
--- a/Documentation/git-config.txt
+++ b/Documentation/git-config.txt
@@ -240,6 +240,14 @@ GIT_CONFIG::
        Using the "--global" option forces this to ~/.gitconfig. Using the
        "--system" option forces this to $(prefix)/etc/gitconfig.
+       Whether to skip reading settings from the system-wide
+       $(prefix)/etc/gitconfig file.  This environment variable can
+       be used along with HOME and XDG_CONFIG_HOME to create a
+       predictable environment for a picky script, or you can set it
+       temporarily to avoid using a buggy /etc/gitconfig file while
+       waiting for someone with sufficient permissions to fix it.
 See also <<FILES>>.

To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to