git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH (v2) 1/2] rebase: fix --onto A...B parsing and add tests

From
Nanako Shiraishi <nanako3@lavabit.com>
Date
Jan 7, 2010, 11:05 UTC
Message-ID
<20100107200502.6117@nanako3.lavabit.com>
In-Reply-To
<7vocl7yxef.fsf@alter.siamese.dyndns.org>

The previous patch didn't parse "rebase --onto A...B" correctly when A isn't an empty string. It also tried to be careful to notice a case in which there are more than one merge bases, but forgot to give --all option to merge-base, making the test pointless.

Fix these problems and add a test script to verify. Improvements to the script to parse A...B syntax was taken from review comments by Johannes Schindelin.

Signed-off-by: しらいし ななこ <nanako3@lavabit.com>
---
 git-rebase.sh                    |   33 ++++++++++-------
 t/t3415-rebase-onto-threedots.sh |   75 ++++++++++++++++++++++++++++++++++++++
 2 files changed, 94 insertions(+), 14 deletions(-)
 create mode 100755 t/t3415-rebase-onto-threedots.sh
diff --git a/git-rebase.sh b/git-rebase.sh
index 6503113..9bd8974 100755
--- a/git-rebase.sh
+++ b/git-rebase.sh
@@ -419,22 +419,27 @@ fi
 
 # Make sure the branch to rebase onto is valid.
 onto_name=${newbase-"$upstream_name"}
-if	left=$(expr "$onto_name" : '\(.*\)\.\.\.') &&
-	right=$(expr "$onto_name" : '\.\.\.\(.*\)$') &&
-	: ${left:=HEAD} ${right:=HEAD} &&
-	onto=$(git merge-base "$left" "$right")
-then
-	case "$onto" in
-	?*"$LF"?*)
-		die "$onto_name: there are more than one merge bases"
-		;;
-	'')
+case "$onto_name" in
+*...*)
+	if	left=${onto_name%...*} right=${onto_name#*...} &&
+		onto=$(git merge-base --all ${left:-HEAD} ${right:-HEAD})
+	then
+		case "$onto" in
+		?*"$LF"?*)
+			die "$onto_name: there are more than one merge bases"
+			;;
+		'')
+			die "$onto_name: there is no merge base"
+			;;
+		esac
+	else
 		die "$onto_name: there is no merge base"
-		;;
-	esac
-else
+	fi
+	;;
+*)
 	onto=$(git rev-parse --verify "${onto_name}^0") || exit
-fi
+	;;
+esac
 
 # If a hook exists, give it a chance to interrupt
 run_pre_rebase_hook "$upstream_arg" "$@"
diff --git a/t/t3415-rebase-onto-threedots.sh b/t/t3415-rebase-onto-threedots.sh
new file mode 100755
index 0000000..da378c4
--- /dev/null
+++ b/t/t3415-rebase-onto-threedots.sh
@@ -0,0 +1,75 @@
+#!/bin/sh
+
+test_description='git rebase --onto A...B'
+
+. ./test-lib.sh
+. "$TEST_DIRECTORY/lib-rebase.sh"
+
+# Rebase only the tip commit of "topic" on merge base between "master"
+# and "topic".  Cannot do this for "side" with "master" because there
+# is no single merge base.
+#
+#
+#	    F---G topic                             G'
+#	   /                                       /
+# A---B---C---D---E master      -->       A---B---C---D---E
+#      \   \ /
+#	\   x
+#	 \ / \ 
+#	  H---I---J---K side
+
+test_expect_success setup '
+	test_commit A &&
+	test_commit B &&
+	git branch side &&
+	test_commit C &&
+	git branch topic &&
+	git checkout side &&
+	test_commit H &&
+	git checkout master &&
+	test_tick &&
+	git merge H &&
+	git tag D &&
+	test_commit E &&
+	git checkout topic &&
+	test_commit F &&
+	test_commit G &&
+	git checkout side &&
+	test_tick &&
+	git merge C &&
+	git tag I &&
+	test_commit J &&
+	test_commit K
+'
+
+test_expect_success 'rebase --onto master...topic' '
+	git reset --hard &&
+	git checkout topic &&
+	git reset --hard G &&
+
+	git rebase --onto master...topic F &&
+	git rev-parse HEAD^1 >actual &&
+	git rev-parse C^0 >expect &&
+	test_cmp expect actual
+'
+
+test_expect_success 'rebase --onto master...' '
+	git reset --hard &&
+	git checkout topic &&
+	git reset --hard G &&
+
+	git rebase --onto master... F &&
+	git rev-parse HEAD^1 >actual &&
+	git rev-parse C^0 >expect &&
+	test_cmp expect actual
+'
+
+test_expect_success 'rebase --onto master...side' '
+	git reset --hard &&
+	git checkout side &&
+	git reset --hard K &&
+
+	test_must_fail git rebase --onto master...side J
+'
+
+test_done
-- 
1.6.6.53.g75f61




-- 
Nanako Shiraishi
http://ivory.ap.teacup.com/nanako3/
Previous: Junio C HamanoNext: Nanako Shiraishi
Message 22 of 32 in “What's cooking in git.git (Jan 2010, #01; Mon, 04)”
  1. Junio C HamanoJan 4, 2010
  2. Matthieu MoyJan 4, 2010
  3. Junio C HamanoJan 4, 2010
  4. Johannes SixtJan 4, 2010
  5. Junio C HamanoJan 5, 2010
  6. Jeff KingJan 5, 2010
  7. Junio C HamanoJan 5, 2010
  8. Johannes SixtJan 5, 2010
  9. Junio C HamanoJan 6, 2010
  10. Johannes SixtJan 6, 2010
  11. Junio C HamanoJan 6, 2010
  12. Junio C HamanoJan 5, 2010
  13. Jeff KingJan 5, 2010
  14. Tay Ray ChuanJan 5, 2010
  15. Teach --[no-]rerere-autoupdate option to merge, revert and friendsJunio C Hamano, Jan 5, 2010
  16. Johan HerlandJan 5, 2010
  17. Ilari LiusvaaraJan 5, 2010
  18. Junio C HamanoJan 6, 2010
  19. Nanako ShiraishiJan 6, 2010
  20. Johannes SchindelinJan 6, 2010
  21. Junio C HamanoJan 6, 2010
  22. 1/2 rebase: fix --onto A...B parsing and add testsNanako Shiraishi, Jan 7, 2010
  23. 2/2 rebase -i: teach --onto A...B syntaxNanako Shiraishi, Jan 7, 2010
  24. Junio C HamanoJan 7, 2010
  25. Johannes SixtJan 7, 2010
  26. Avery PennarunJan 8, 2010
  27. Sverre RabbelierJan 8, 2010
  28. Avery PennarunJan 8, 2010
  29. Sverre RabbelierJan 8, 2010
  30. A Large Angry SCMJan 8, 2010
  31. Johannes SchindelinJan 9, 2010
  32. Avery PennarunJan 9, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.