From: Michael J Gruber <git@drmicha.warpmail.net>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>
Subject: [PATCH 0/2] Allow running the test suite against installed git
Date: Fri, 13 Mar 2009 16:45:14 +0100 [thread overview]
Message-ID: <1236959116-3334-1-git-send-email-git@drmicha.warpmail.net> (raw)
Part 1 corrects only an inconsistency which does not matter as long as
you run tests against git compiled in a checkout only: There,
$GIT_EXEC_PATH contains git, in general it does not.
Part 2 allows running the test suite against a git installed anywhere in
the file system. This has at least 2 use cases:
- Test an installed distro package after the installation.
- Run easily current tests against older versions, or vice versa, if you
have those versions installed somewhere.
Note that one still needs git compiled in git.git for test helpers etc.,
and also because I did not adjust the paths to templates and such. I did
not really feel a need for that.
Also, t0000 there is still one explicit use of "../git" which is fine
because it simply tests for the presence of a built, which we need
anyways.
Michael J Gruber (2):
test-lib.sh: Test for presence of git-init in the right path.
test-lib.sh: Allow running the test suite against installed git
t/test-lib.sh | 12 +++++++++---
1 files changed, 9 insertions(+), 3 deletions(-)
next reply other threads:[~2009-03-13 15:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-13 15:45 Michael J Gruber [this message]
2009-03-13 15:45 ` [PATCH 1/2] test-lib.sh: Test for presence of git-init in the right path Michael J Gruber
2009-03-13 15:45 ` [PATCH 2/2] test-lib.sh: Allow running the test suite against installed git 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-1-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).