From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Daniel Barkalow <barkalow@iabervon.org>,
Pieter de Bie <pdebie@ai.rug.nl>,
Git Mailinglist <git@vger.kernel.org>
Subject: Re: [PATCH 1/2] clone: respect the settings in $HOME/.gitconfig and /etc/gitconfig
Date: Mon, 30 Jun 2008 02:40:32 -0400 [thread overview]
Message-ID: <20080630064031.GA30600@sigill.intra.peff.net> (raw)
In-Reply-To: <7vskuv30e6.fsf@gitster.siamese.dyndns.org>
On Sun, Jun 29, 2008 at 11:25:05PM -0700, Junio C Hamano wrote:
> > Honestly, GIT_CONFIG is purely for scripts like git-svn that muck with
> > files that are in the config format to have a way to make sure that they
> > access the file they intend to, and being able to use GIT_CONFIG to keep
> > git programs from reading from $HOME/.gitconfig is primarily for giving
> > our test scripts repeatable environment, nothing more.
[...]
> Of course, that would have downsides as well. Now git-clone tests cannot
> be sanely written without setting $HOME to somewhere stable; otherwise
> they can be randomly affected by buggy $HOME/.gitconfig files the end user
> may have.
I thought we went through all of this before, and it led to 8bfa6bd6.
The test scripts set GIT_CONFIG_NOSYSTEM and GIT_CONFIG_NOGLOBAL to
achieve the same suppression effect.
-Peff
next prev parent reply other threads:[~2008-06-30 6:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-27 9:35 Using url.insteadOf in git-clone Pieter de Bie
2008-06-27 12:55 ` [PATCH 1/2] clone: respect the settings in $HOME/.gitconfig and /etc/gitconfig Johannes Schindelin
2008-06-27 12:56 ` [PATCH 2/2] clone: respect url.insteadOf setting in global configs Johannes Schindelin
2008-06-27 16:08 ` Daniel Barkalow
2008-06-29 20:12 ` Pieter de Bie
2008-06-29 21:50 ` Johannes Schindelin
2008-06-27 16:05 ` [PATCH 1/2] clone: respect the settings in $HOME/.gitconfig and /etc/gitconfig Daniel Barkalow
2008-06-27 22:40 ` Junio C Hamano
2008-06-29 18:31 ` Daniel Barkalow
2008-06-29 20:36 ` Junio C Hamano
2008-06-29 21:49 ` Johannes Schindelin
2008-06-29 22:47 ` Daniel Barkalow
2008-06-30 0:41 ` Johannes Schindelin
2008-06-30 1:54 ` Daniel Barkalow
2008-06-30 1:20 ` Junio C Hamano
2008-06-30 2:21 ` Daniel Barkalow
2008-06-30 3:47 ` Daniel Barkalow
2008-06-30 11:57 ` Johannes Schindelin
2008-06-30 16:47 ` Daniel Barkalow
2008-06-30 6:20 ` Junio C Hamano
2008-06-30 6:25 ` Junio C Hamano
2008-06-30 6:40 ` Jeff King [this message]
2008-06-30 6:44 ` Junio C Hamano
2008-06-30 11:37 ` Johannes Schindelin
2008-06-27 17:11 ` Using url.insteadOf in git-clone Junio C Hamano
2008-06-29 18:59 ` Pieter de Bie
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=20080630064031.GA30600@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pdebie@ai.rug.nl \
/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).