From: Junio C Hamano <junkio@cox.net>
To: Mark Allen <mrallen1@yahoo.com>
Cc: git@vger.kernel.org
Subject: Re: Failure in t6021 on Red Hat Enterprise Linux 4
Date: Wed, 07 Dec 2005 10:54:24 -0800 [thread overview]
Message-ID: <7vslt4rb4v.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20051207181225.67737.qmail@web34304.mail.mud.yahoo.com> (Mark Allen's message of "Wed, 7 Dec 2005 10:12:24 -0800 (PST)")
Mark Allen <mrallen1@yahoo.com> writes:
> So, basically the problem is that the subprocess.py module is
> in the compat directory, and by default (I think)..
Ah, you are right.
Just like we fix PATH and GIT_EXEC_PATH during the test
execution, we need to do something with PYTHONPATH environment
variable (this one is _without_ underscore), I think.
next prev parent reply other threads:[~2005-12-07 18:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-07 16:49 Failure in t6021 on Red Hat Enterprise Linux 4 Mark Allen
2005-12-07 17:38 ` Junio C Hamano
2005-12-07 18:12 ` Mark Allen
2005-12-07 18:54 ` Junio C Hamano [this message]
2005-12-08 6:07 ` [PATCH] Make sure we use compat/subprocess.py with Python 2.3 while running tests Junio C Hamano
2005-12-08 17:04 ` Mark Allen
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=7vslt4rb4v.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=mrallen1@yahoo.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).