From: "Jan Krüger" <jk@jk.gs>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git ML <git@vger.kernel.org>
Subject: Re: [PATCH] Documentation: mention environment variables GIT_CONFIG_NO(GLOBAL|SYSTEM)
Date: Mon, 4 Oct 2010 08:31:06 +0200 [thread overview]
Message-ID: <20101004083106.74623cd5@jk.gs> (raw)
In-Reply-To: <7vvd5ieu29.fsf@alter.siamese.dyndns.org>
--- Junio C Hamano <gitster@pobox.com> wrote:
> Aren't they undocumented because the use case for them is pretty much
> limited to the test scripts and nowhere else? I am not absolutely
> sure about GIT_CONFIG_NOGLOBAL, but NOSYSTEM surely was started that
> way.
I don't know. I found them when someone on IRC was looking for a way to
bypass an insteadOf setting in his ~/.gitconfig file, so I guess that
there is an actual use case for some.
-Jan
prev parent reply other threads:[~2010-10-04 6:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-03 21:53 [PATCH] Documentation: mention environment variables GIT_CONFIG_NO(GLOBAL|SYSTEM) Jan Krüger
2010-10-03 23:10 ` Sverre Rabbelier
2010-10-03 23:27 ` Junio C Hamano
2010-10-04 6:31 ` Jan Krüger [this message]
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=20101004083106.74623cd5@jk.gs \
--to=jk@jk.gs \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).