From: Michael J Gruber <git@drmicha.warpmail.net>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>
Subject: [PATCH 1/2] test-lib.sh: Test for presence of git-init in the right path.
Date: Fri, 13 Mar 2009 16:45:15 +0100 [thread overview]
Message-ID: <1236959116-3334-2-git-send-email-git@drmicha.warpmail.net> (raw)
In-Reply-To: <1236959116-3334-1-git-send-email-git@drmicha.warpmail.net>
It just happens so that when GIT_EXEC_PATH points to a compiled checkout
of git.git it contains "git". Since this is not true in general make
test-lib check for "git-init" which is always in GIT_EXEC_PATH.
Signed-off-by: Michael J Gruber <git@drmicha.warpmail.net>
---
t/test-lib.sh | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/t/test-lib.sh b/t/test-lib.sh
index 7a847ec..b9da86e 100644
--- a/t/test-lib.sh
+++ b/t/test-lib.sh
@@ -454,7 +454,7 @@ test_create_repo () {
repo="$1"
mkdir -p "$repo"
cd "$repo" || error "Cannot setup test environment"
- "$GIT_EXEC_PATH/git" init "--template=$owd/../templates/blt/" >&3 2>&4 ||
+ "$GIT_EXEC_PATH/git-init" "--template=$owd/../templates/blt/" >&3 2>&4 ||
error "cannot run git init -- have you built things yet?"
mv .git/hooks .git/hooks-disabled
cd "$owd"
--
1.6.2.149.g6462
next prev parent reply other threads:[~2009-03-13 15:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-13 15:45 [PATCH 0/2] Allow running the test suite against installed git Michael J Gruber
2009-03-13 15:45 ` Michael J Gruber [this message]
2009-03-13 15:45 ` [PATCH 2/2] test-lib.sh: " Michael J Gruber
2009-03-14 20:25 ` Junio C Hamano
2009-03-16 17:03 ` [PATCHv2 0/2] " Michael J Gruber
2009-03-16 17:03 ` [PATCHv2 1/2] test-lib.sh: Test for presence of git-init in the right path Michael J Gruber
2009-03-16 17:03 ` [PATCHv2 2/2] test-lib.sh: Allow running the test suite against installed git Michael J Gruber
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=1236959116-3334-2-git-send-email-git@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--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).