From: Junio C Hamano <gitster@pobox.com>
To: Thomas Rast <trast@inf.ethz.ch>
Cc: "David A. Greene" <dag@cray.com>, <greened@obbligato.org>,
<git@vger.kernel.org>
Subject: Re: [PATCH 2/2] Support Out-Of-Tree Valgrind Tests
Date: Tue, 06 Mar 2012 10:43:25 -0800 [thread overview]
Message-ID: <7veht5tvsi.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <878vje86cy.fsf@thomas.inf.ethz.ch> (Thomas Rast's message of "Tue, 6 Mar 2012 09:46:05 +0100")
Thomas Rast <trast@inf.ethz.ch> writes:
> Don't we, right now, get stuff as follows:
>
> item path
> --------------------------------------------
> test-lib.sh $TEST_DIRECTORY
> git $GIT_BUILD_DIR/bin-wrappers
> valgrind.sh $TEST_DIRECTORY/valgrind
> git (with --valgrind) $TEST_DIRECTORY/valgrind/bin
>
> You are saying this must change to an entirely new path
>
> valgrind.sh $GIT_VALGRIND_TOOLS
> git (with --valgrind) $GIT_VALGRIND_TOOLS/bin
>
> but what's wrong with simply
>
> valgrind.sh $GIT_BUILD_DIR/t/valgrind
> git (with --valgrind) $TEST_DIRECTORY/valgrind/bin
>
> In the common case of t/, these just map to what we had before. In the
> out-of-tree case, we'd create valgrind/bin in the test directory for the
> *temporary* stuff, and still look for the wrapping valgrind.sh in the
> git tree.
Sounds sane. Simple is good.
No matter what happens to this particular patch, could we have the
above table (the final version of it, that is) in t/README or
something, please?
Thanks.
next prev parent reply other threads:[~2012-03-06 18:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-04 23:23 [PATCH 1/2] Allow Overriding GIT_BUILD_DIR greened
2012-03-04 23:23 ` [PATCH 2/2] Support Out-Of-Tree Valgrind Tests greened
2012-03-05 7:53 ` Thomas Rast
2012-03-05 18:11 ` David A. Greene
2012-03-06 8:46 ` Thomas Rast
2012-03-06 14:40 ` David A. Greene
2012-03-06 18:49 ` Junio C Hamano
2012-03-06 22:12 ` David A. Greene
2012-03-06 22:21 ` Junio C Hamano
2012-03-06 22:37 ` Junio C Hamano
2012-03-06 23:00 ` David A. Greene
2012-03-06 23:12 ` Junio C Hamano
2012-03-06 22:54 ` David A. Greene
2012-03-06 18:43 ` Junio C Hamano [this message]
2012-03-05 6:33 ` [PATCH 1/2] Allow Overriding GIT_BUILD_DIR Junio C Hamano
2012-03-05 18:10 ` David A. Greene
2012-03-05 20:08 ` Junio C Hamano
2012-03-06 14:21 ` David A. Greene
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=7veht5tvsi.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=dag@cray.com \
--cc=git@vger.kernel.org \
--cc=greened@obbligato.org \
--cc=trast@inf.ethz.ch \
/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).