From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Gerrit Pape <pape@smarden.org>, git@vger.kernel.org
Subject: Re: [PATCH] t9600-cvsimport.sh: set HOME before checking for cvsps availability
Date: Wed, 26 Mar 2008 23:28:34 -0400 [thread overview]
Message-ID: <20080327032834.GA5417@coredump.intra.peff.net> (raw)
In-Reply-To: <7v8x05e5fa.fsf@gitster.siamese.dyndns.org>
On Wed, Mar 26, 2008 at 10:55:21AM -0700, Junio C Hamano wrote:
> In the longer run, we probably would want to do something similar for all
> tests to ensure a stable testing environment, don't we? $HOME/.gitconfig
> may affect the way tested programs behave otherwise.
We used to, as per a patch from Gerrit long ago:
2eb10ac... Set $HOME for selftests
but it was removed during Dscho's config fix:
8565d2d... Make tests independent of global config files
which used GIT_CONFIG instead. But that had some problems, which I fixed
in:
8bfa6bd... fix config reading in tests
and that patch explicitly suppresses lookup in the ~/.gitconfig and
/etc/gitconfig files (implemented by ab88c363).
So I think all is correct with .gitconfig files. However, I still think
setting HOME is a good idea, because it eliminates one more variable in
test runs. In particular, I know I have gotten cvsps into a funny state
that was resolved by removing the ~/.cvsps cache. So it's probably worth
doing as a preventative measure, even if it doesn't fix a specific bug.
-Peff
next prev parent reply other threads:[~2008-03-27 3:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-26 17:34 [PATCH] t9600-cvsimport.sh: set HOME before checking for cvsps availability Gerrit Pape
2008-03-26 17:55 ` Junio C Hamano
2008-03-27 3:28 ` Jeff King [this message]
2008-03-27 11:07 ` Johannes Schindelin
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=20080327032834.GA5417@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pape@smarden.org \
/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