From: Junio C Hamano <gitster@pobox.com>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: git@vger.kernel.org
Subject: Re: [RFC] Support TEST_GIT_PATH variable for the path for the git to test
Date: Tue, 26 Feb 2008 13:01:48 -0800 [thread overview]
Message-ID: <7vhcfv4ekj.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.LNX.1.00.0802261539130.19665@iabervon.org> (Daniel Barkalow's message of "Tue, 26 Feb 2008 15:46:17 -0500 (EST)")
Daniel Barkalow <barkalow@iabervon.org> writes:
>> Ok, so even "installed" case need to rely on "test-blah" we build.
>
> Right. Would it be okay to build those into t/helpers/* or something,
> instead of into the project root, so that they're just naturally separate
> from the actual program?
Yeah, it sounds like a plan.
prev parent reply other threads:[~2008-02-26 21:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-25 23:21 [RFC] Support TEST_GIT_PATH variable for the path for the git to test Daniel Barkalow
2008-02-26 0:00 ` Junio C Hamano
2008-02-26 18:02 ` Daniel Barkalow
2008-02-26 18:46 ` Junio C Hamano
2008-02-26 19:16 ` Daniel Barkalow
2008-02-26 20:22 ` Junio C Hamano
2008-02-26 20:46 ` Daniel Barkalow
2008-02-26 21:01 ` Junio C Hamano [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=7vhcfv4ekj.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).