From: Jeff King <peff@peff.net>
To: Lars Noschinski <lars@public.noschinski.de>
Cc: git@vger.kernel.org, fabian.emmes@rwth-aachen.de
Subject: Re: [PATCH] Testsuite: Unset CVS_SERVER
Date: Thu, 17 Jul 2008 13:53:03 -0400 [thread overview]
Message-ID: <20080717175303.GA8197@sigill.intra.peff.net> (raw)
In-Reply-To: <1216288877-12140-2-git-send-email-lars@public.noschinski.de>
On Thu, Jul 17, 2008 at 12:01:13PM +0200, Lars Noschinski wrote:
> The CVS_SERVER environment variable cane cause some of the cvsimport tests
> to fail. So unset this variable at the beginning of the test script.
This is definitely an improvement. However, the cvs manual lists a
number of CVS* variables. Perhaps it would be better to simply scrub the
environment of any variable matching that pattern? I don't know how
commonly used some of the other ones are.
-Peff
next prev parent reply other threads:[~2008-07-17 17:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-17 10:01 Some cvs related fixes and enhancements Lars Noschinski
2008-07-17 10:01 ` [PATCH] Testsuite: Unset CVS_SERVER Lars Noschinski
2008-07-17 10:01 ` [PATCH] cvsserver: Add support for packed refs Lars Noschinski
2008-07-17 10:01 ` [PATCH] cvsserver: Add testsuite " Lars Noschinski
2008-07-17 10:01 ` [PATCH] cvsserver: Add cvs co -c support Lars Noschinski
2008-07-17 10:01 ` [PATCH] testsuite for cvs co -c Lars Noschinski
2008-07-17 11:54 ` [PATCH] cvsserver: Add testsuite for packed refs Johannes Schindelin
2008-07-17 11:50 ` [PATCH] cvsserver: Add support " Johannes Schindelin
2008-07-17 12:40 ` Lars Noschinski
2008-07-17 11:45 ` [PATCH] Testsuite: Unset CVS_SERVER Johannes Schindelin
2008-07-17 17:53 ` Jeff King [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-07-17 17:00 Some cvs related fixes and enhancements v2 Lars Noschinski
2008-07-17 17:00 ` [PATCH] Testsuite: Unset CVS_SERVER Lars Noschinski
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=20080717175303.GA8197@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=fabian.emmes@rwth-aachen.de \
--cc=git@vger.kernel.org \
--cc=lars@public.noschinski.de \
/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).