From: greened@obbligato.org
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Mar 2012, #09; Mon, 26)
Date: Mon, 26 Mar 2012 20:16:02 -0500 [thread overview]
Message-ID: <87limmdest.fsf@smith.obbligato.org> (raw)
In-Reply-To: <7vzkb3kl6f.fsf@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Mon, 26 Mar 2012 16:16:24 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> * dg/test-from-elsewhere (2012-03-04) 2 commits
> - Support out-of-tree Valgrind tests
> - Allow overriding GIT_BUILD_DIR
>
> Better support for out-of-tree test scripts, but it appears that the
> approach needs to be rethought. By repointing TEST_DIRECTORY to a
> directory other than $(pwd)/.., an out of place test script can reach
> test helpers and freshly built Git relative to it (GIT_BUILD_DIR is
> a mere short-hand for $TEST_DIRECTORY/..).
>
> Discussion stalled.
We don't need this anymore, so go ahead and drop it.
-Dave
prev parent reply other threads:[~2012-03-27 1:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-26 23:16 What's cooking in git.git (Mar 2012, #09; Mon, 26) Junio C Hamano
2012-03-27 1:16 ` greened [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=87limmdest.fsf@smith.obbligato.org \
--to=greened@obbligato.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).