git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jul 2012, #07; Mon, 23)
Date: Tue, 24 Jul 2012 07:42:18 -0700	[thread overview]
Message-ID: <7vfw8hgr05.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20120724135838.GB14422@sigill.intra.peff.net> (Jeff King's message of "Tue, 24 Jul 2012 09:58:38 -0400")

Jeff King <peff@peff.net> writes:

> On Mon, Jul 23, 2012 at 10:10:00PM -0700, Junio C Hamano wrote:
>
>> * jc/test-lib-source-build-options-early (2012-06-24) 1 commit
>>  - test-lib: reorder and include GIT-BUILD-OPTIONS a lot earlier
>> 
>> Reorders t/test-lib.sh so that we dot-source GIT-BUILD-OPTIONS that
>> records the shell and Perl the user told us to use with Git a lot
>> early, so that test-lib.sh script itself can use "$PERL_PATH" in
>> one of its early operations.
>> 
>> Needs to be eyeballed by people who run tests with exotic options
>> like valgrind, --root=/dev/shm/somewhere, etc.
>
> I'm such a people. Both --valgrind and --root work OK with the patch.
> Reading the patch, I don't see any other problematic options, either.

Thanks; I've been running tests for 'pu' with --root pointing
elsewhere as well.  I probably should push this forward before the
tree gets busy again post relesae.

      reply	other threads:[~2012-07-24 14:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-24  5:10 What's cooking in git.git (Jul 2012, #07; Mon, 23) Junio C Hamano
2012-07-24 13:58 ` Jeff King
2012-07-24 14:42   ` 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=7vfw8hgr05.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    /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).