{"thread":{"id":"25325","subject":"[PATCH] Documentation: mention environment variables GIT_CONFIG_NO(GLOBAL|SYSTEM)","startedAt":"2010-10-03T21:53:29Z","lastAt":"2010-10-04T06:31:06Z","messageCount":4,"participants":["Jan Krüger","Sverre Rabbelier","Junio C Hamano"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"152417","messageId":"20101003235329.6f4d2572@jk.gs","threadId":"25325","inReplyTo":null,"subject":"[PATCH] Documentation: mention environment variables GIT_CONFIG_NO(GLOBAL|SYSTEM)","fromName":"Jan Krüger","fromEmail":"jk@jk.gs","sentAt":"2010-10-03T21:53:29Z","receivedAt":"2010-10-03T21:53:29Z","isPatch":true,"sender":{"key":"jk@jk.gs","avatar":"https://avatars.githubusercontent.com/u/1774?v=4"},"body":"The environment variables GIT_CONFIG_NOGLOBAL and GIT_CONFIG_NOSYSTEM\nwhich have the opposite effect of the --global and --system switches to\ngit-config are completely undocumented. This mentions them in the\n'files' and 'environment' sections of the manpage for git-config where\nGIT_CONFIG is already mentioned.\n\nSigned-off-by: Jan Krüger <jk@jk.gs>\n---\n Documentation/git-config.txt |   10 ++++++++++\n 1 files changed, 10 insertions(+), 0 deletions(-)\n\ndiff --git a/Documentation/git-config.txt b/Documentation/git-config.txt\nindex 543dd64..c3ea29c 100644\n--- a/Documentation/git-config.txt\n+++ b/Documentation/git-config.txt\n@@ -210,6 +210,9 @@ variables. The '--global' and the '--system' options will limit the file used\n to the global or system-wide file respectively. The GIT_CONFIG environment\n variable has a similar effect, but you can specify any filename you want.\n \n+You can also set the environment GIT_CONFIG_NOGLOBAL and GIT_CONFIG_NOSYSTEM\n+to explicitly prevent git from falling back to global/system settings.\n+\n \n ENVIRONMENT\n -----------\n@@ -219,6 +222,14 @@ GIT_CONFIG::\n \tUsing the \"--global\" option forces this to ~/.gitconfig. Using the\n \t\"--system\" option forces this to $(prefix)/etc/gitconfig.\n \n+GIT_CONFIG_NOGLOBAL::\n+\tIf set to true, do not use the global configuration file\n+\tin ~/.gitconfig.\n+\n+GIT_CONFIG_NOSYSTEM::\n+\tIf set to true, do not use the system-wide configuration file in\n+\t/etc/gitconfig.\n+\n See also <<FILES>>.\n \n \n-- \n1.7.2.3.392.g02377.dirty\n"},{"id":"152426","messageId":"AANLkTimkDEff5dzO+PDR44vSq9JQ7Junj+Lwm30Fy1Vr@mail.gmail.com","threadId":"25325","inReplyTo":"20101003235329.6f4d2572@jk.gs","subject":"Re: [PATCH] Documentation: mention environment variables GIT_CONFIG_NO(GLOBAL|SYSTEM)","fromName":"Sverre Rabbelier","fromEmail":"srabbelier@gmail.com","sentAt":"2010-10-03T23:10:08Z","receivedAt":"2010-10-03T23:10:08Z","isPatch":true,"sender":{"key":"srabbelier@gmail.com","avatar":"https://avatars.githubusercontent.com/u/3098?v=4"},"body":"Heya,\n\nOn Sun, Oct 3, 2010 at 23:53, Jan Krüger <jk@jk.gs> wrote:\n> The environment variables GIT_CONFIG_NOGLOBAL and GIT_CONFIG_NOSYSTEM\n> which have the opposite effect of the --global and --system switches to\n> git-config are completely undocumented. This mentions them in the\n> 'files' and 'environment' sections of the manpage for git-config where\n> GIT_CONFIG is already mentioned.\n\nNice.\n\n> +GIT_CONFIG_NOGLOBAL::\n> +       If set to true, do not use the global configuration file\n> +       in ~/.gitconfig.\n> +\n> +GIT_CONFIG_NOSYSTEM::\n> +       If set to true, do not use the system-wide configuration file in\n> +       /etc/gitconfig.\n> +\n\nIf there are a '--no-global' and '--no-system', would it good to\nmention those too? Something like: \"If set to true, do not use the\nsystem-wide configuration file in /etc/gitconfig, equivalent to\n--no-global.\"?\n\n-- \nCheers,\n\nSverre Rabbelier\n"},{"id":"152429","messageId":"7vvd5ieu29.fsf@alter.siamese.dyndns.org","threadId":"25325","inReplyTo":"20101003235329.6f4d2572@jk.gs","subject":"Re: [PATCH] Documentation: mention environment variables GIT_CONFIG_NO(GLOBAL|SYSTEM)","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2010-10-03T23:27:10Z","receivedAt":"2010-10-03T23:27:10Z","isPatch":true,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Jan Krüger <jk@jk.gs> writes:\n\n> The environment variables GIT_CONFIG_NOGLOBAL and GIT_CONFIG_NOSYSTEM\n> which have the opposite effect of the --global and --system switches to\n> git-config are completely undocumented. This mentions them in the\n> 'files' and 'environment' sections of the manpage for git-config where\n> GIT_CONFIG is already mentioned.\n>\n> Signed-off-by: Jan Krüger <jk@jk.gs>\n\nAren't they undocumented because the use case for them is pretty much\nlimited to the test scripts and nowhere else?  I am not absolutely sure\nabout GIT_CONFIG_NOGLOBAL, but NOSYSTEM surely was started that way.\n"},{"id":"152464","messageId":"20101004083106.74623cd5@jk.gs","threadId":"25325","inReplyTo":"7vvd5ieu29.fsf@alter.siamese.dyndns.org","subject":"Re: [PATCH] Documentation: mention environment variables GIT_CONFIG_NO(GLOBAL|SYSTEM)","fromName":"Jan Krüger","fromEmail":"jk@jk.gs","sentAt":"2010-10-04T06:31:06Z","receivedAt":"2010-10-04T06:31:06Z","isPatch":true,"sender":{"key":"jk@jk.gs","avatar":"https://avatars.githubusercontent.com/u/1774?v=4"},"body":"--- Junio C Hamano <gitster@pobox.com> wrote:\n\n> Aren't they undocumented because the use case for them is pretty much\n> limited to the test scripts and nowhere else?  I am not absolutely\n> sure about GIT_CONFIG_NOGLOBAL, but NOSYSTEM surely was started that\n> way.\n\nI don't know. I found them when someone on IRC was looking for a way to\nbypass an insteadOf setting in his ~/.gitconfig file, so I guess that\nthere is an actual use case for some.\n\n-Jan\n"}]}