git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jon Seymour <jon.seymour@gmail.com>
To: git@vger.kernel.org
Cc: Jon Seymour <jon.seymour@gmail.com>
Subject: [PATCH 13/23] Introduce --reachable
Date: Sat, 23 Apr 2011 17:22:42 +1000	[thread overview]
Message-ID: <1303543372-77843-14-git-send-email-jon.seymour@gmail.com> (raw)
In-Reply-To: <1303543372-77843-1-git-send-email-jon.seymour@gmail.com>

reachable
---
 Documentation/git-test.txt |    2 +
 git-conditions-lib.sh      |   14 ++++++
 t/t1520-test.sh            |  101 ++++++++++++++++++++++++++++++++++++++++++++
 3 files changed, 117 insertions(+), 0 deletions(-)

diff --git a/Documentation/git-test.txt b/Documentation/git-test.txt
index f76aa38..e28ed88 100644
--- a/Documentation/git-test.txt
+++ b/Documentation/git-test.txt
@@ -86,6 +86,8 @@ CONDITIONS
 	Tests if the specified commit does (not) exist.
 '--checked-out'|'--not-checked-out branch'::
         Tests if the specified branch is (not) checked out.
+'--reachable'|'--not-reachable' first second::
+	Tests if the first commit is (not) reachable from the second.
 
 EXTENDING THE CONDITION LIBRARY
 -------------------------------
diff --git a/git-conditions-lib.sh b/git-conditions-lib.sh
index 3eccc19..0223fcd 100644
--- a/git-conditions-lib.sh
+++ b/git-conditions-lib.sh
@@ -136,5 +136,19 @@ check_checked_out_1()
 
 }
 
+check_reachable_2()
+{
+	first=$(git rev-parse --quiet --verify "$1" 2>/dev/null) || die "'$1' is not a commit"
+	second=$(git rev-parse --quiet --verify "$2" 2>/dev/null) || die "'$2' is not a commit"
+	if test "$first" = "$second" \
+                -o -z "$(git rev-list -n1 "$first" ^"$second")" 
+	then
+		echo "'$1' is reachable from '$2'."
+	else
+		echo "'$1' is not reachable from '$2'."
+		false
+	fi     
+}
+
 
 fi
diff --git a/t/t1520-test.sh b/t/t1520-test.sh
index bb39050..3e33f8a 100755
--- a/t/t1520-test.sh
+++ b/t/t1520-test.sh
@@ -298,4 +298,105 @@ test_expect_success 'git test --detached # when detached' \
 	git test --detached
 '
 
+
+test_expect_success 'git test --reachable #should fail' \
+'
+	test_must_fail git test --reachable
+'
+
+test_expect_success 'git test --not-reachable #should fail' \
+'
+	test_must_fail git test --reachable
+'
+
+test_expect_success 'git test --reachable A #should fail' \
+'
+	test_must_fail git test --reachable A
+'
+
+test_expect_success 'git test --not-reachable A #should fail' \
+'
+	test_must_fail git test --not-reachable A
+'
+
+test_expect_success 'git test --reachable does-not-exist-1 does-not-exist-2 #should fail' \
+'
+	test_must_fail git test --reachable does-not-exist-1 does-not-exist-2
+'
+
+test_expect_success 'git test --not-reachable does-not-exist-1 does-not-exist-2 #should fail' \
+'
+	test_must_fail git test --not-reachable does-not-exist-1 does-not-exist-2
+'
+
+test_expect_success 'git test --reachable does-not-exist-1 A #should fail' \
+'
+	test_must_fail git test --reachable does-not-exist-1 A
+'
+
+test_expect_success 'git test --not-reachable does-not-exist-1 A #should fail' \
+'
+	test_must_fail git test --not-reachable does-not-exist-1 A
+'
+
+test_expect_success 'git test --reachable A does-not-exist-2 #should fail' \
+'
+	test_must_fail git test --reachable A does-not-exist-2
+'
+
+test_expect_success 'git test --not-reachable A does-not-exist-2 #should fail' \
+'
+	test_must_fail git test --not-reachable A does-not-exist-2
+'
+
+test_expect_success 'git test --reachable A C' \
+'
+       git test --reachable A C
+'
+
+test_expect_success 'git test --not-reachable A C # should fail' \
+'
+       test_must_fail git test --not-reachable A C
+'
+
+test_expect_success 'git test --reachable C A # should fail' \
+'
+       test_must_fail git test --reachable C A
+'
+
+test_expect_success 'git test --not-reachable C A # should fail' \
+'
+       git test --not-reachable C A
+'
+
+test_expect_success 'git test --reachable C C' \
+'
+       git test --reachable C C
+'
+
+test_expect_success 'git test --not-reachable C C' \
+'
+       test_must_fail git test --not-reachable C C
+'
+
+test_expect_success 'git test --reachable C F' \
+'
+       test_must_fail git test --reachable C F
+'
+
+test_expect_success 'git test --not-reachable C F' \
+'
+       git test --not-reachable C F
+'
+
+test_expect_success 'git test --reachable F C' \
+'
+       test_must_fail git test --reachable F C
+'
+
+test_expect_success 'git test --not-reachable F C' \
+'
+       git test --not-reachable F C
+'
+
 test_done
-- 
1.7.5.rc1.23.g7f622

  parent reply	other threads:[~2011-04-23  7:24 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-23  7:22 [PATCH 00/23] RFC: Introducing git-test, git-atomic, git-base and git-work Jon Seymour
2011-04-23  7:22 ` [PATCH 01/23] Introduce git-test.sh and git-test-lib.sh Jon Seymour
2011-04-27 19:11   ` Drew Northup
2011-04-23  7:22 ` [PATCH 02/23] Introduce --unstaged Jon Seymour
2011-04-23  7:22 ` [PATCH 03/23] Introduce --staged Jon Seymour
2011-04-23  7:22 ` [PATCH 04/23] Introduce --untracked Jon Seymour
2011-04-23  7:22 ` [PATCH 05/23] Introduce --conflicted Jon Seymour
2011-04-23  7:22 ` [PATCH 06/23] Introduce --rebasing Jon Seymour
2011-04-23  7:22 ` [PATCH 07/23] Introduce --detached Jon Seymour
2011-04-23  7:22 ` [PATCH 08/23] Introduce --branch-exists Jon Seymour
2011-04-23  7:22 ` [PATCH 09/23] Introduce --tag-exists Jon Seymour
2011-04-23  7:22 ` [PATCH 10/23] Introduce --ref-exists Jon Seymour
2011-04-23  7:22 ` [PATCH 11/23] Introduce --commit-exists Jon Seymour
2011-04-23  7:22 ` [PATCH 12/23] Introduce --checked-out Jon Seymour
2011-04-23  7:22 ` Jon Seymour [this message]
2011-04-23  7:22 ` [PATCH 14/23] Introduce --tree-same Jon Seymour
2011-04-23  7:22 ` [PATCH 15/23] Introduce --same Jon Seymour
2011-04-23  7:22 ` [PATCH 16/23] misc Jon Seymour
2011-04-23  7:22 ` [PATCH 17/23] whitespace fix Jon Seymour
2011-04-23  7:22 ` [PATCH 18/23] tests --conflicted Jon Seymour
2011-04-23  7:22 ` [PATCH 19/23] rebasing: add tests Jon Seymour
2011-04-23  7:22 ` [PATCH 20/23] test: git test cleanups Jon Seymour
2011-04-23  7:22 ` [PATCH 21/23] Introduce git-atomic Jon Seymour
2011-04-23  7:22 ` [PATCH 22/23] Introduce git base Jon Seymour
2011-04-23  7:22 ` [PATCH 23/23] Introduce support for the git-work command Jon Seymour
2011-04-23  9:13 ` [PATCH 00/23] RFC: Introducing git-test, git-atomic, git-base and git-work Peter Baumann
2011-04-23 17:16   ` Jon Seymour
2011-04-23 18:37     ` Jon Seymour
2011-04-24 15:47       ` Jon Seymour

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=1303543372-77843-14-git-send-email-jon.seymour@gmail.com \
    --to=jon.seymour@gmail.com \
    --cc=git@vger.kernel.org \
    /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).