summaryrefslogtreecommitdiff
path: root/t/t3411-rebase-preserve-around-merges.sh
diff options
context:
space:
mode:
authorStephen Haberman <stephen@exigencecorp.com>2008-10-15 07:44:40 (GMT)
committerJunio C Hamano <gitster@pobox.com>2008-10-16 16:23:54 (GMT)
commit80fe82e4eb365773ba6518c4539c9235ea9a8b2e (patch)
tree865b2ff438ef68963f4483ae1cb0264b4c9f490f /t/t3411-rebase-preserve-around-merges.sh
parentd80d6bc146232d81f1bb4bc58e5d89263fd228d4 (diff)
downloadgit-80fe82e4eb365773ba6518c4539c9235ea9a8b2e.zip
git-80fe82e4eb365773ba6518c4539c9235ea9a8b2e.tar.gz
git-80fe82e4eb365773ba6518c4539c9235ea9a8b2e.tar.bz2
rebase-i-p: if todo was reordered use HEAD as the rewritten parent
This seems like the best guess we can make until git sequencer marks are available. That being said, within the context of re-ordering a commit before its parent in todo, I think applying it on top of the current commit seems like a reasonable assumption of what the user intended. Signed-off-by: Stephen Haberman <stephen@exigencecorp.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t3411-rebase-preserve-around-merges.sh')
-rw-r--r--[-rwxr-xr-x]t/t3411-rebase-preserve-around-merges.sh4
1 files changed, 2 insertions, 2 deletions
diff --git a/t/t3411-rebase-preserve-around-merges.sh b/t/t3411-rebase-preserve-around-merges.sh
index f9c549b..aacfaae 100755..100644
--- a/t/t3411-rebase-preserve-around-merges.sh
+++ b/t/t3411-rebase-preserve-around-merges.sh
@@ -80,7 +80,7 @@ test_expect_success 'setup' '
# \ /
# -- C1 --
#
-test_expect_failure 'squash F1 into D1' '
+test_expect_success 'squash F1 into D1' '
FAKE_LINES="1 squash 3 2" git rebase -i -p B1 &&
test "$(git rev-parse HEAD^2)" = "$(git rev-parse branch)" &&
test "$(git rev-parse HEAD~2)" = "$(git rev-parse B1)" &&
@@ -99,7 +99,7 @@ test_expect_failure 'squash F1 into D1' '
#
# And rebase G1..M1 onto E2
-test_expect_failure 'rebase two levels of merge' '
+test_expect_success 'rebase two levels of merge' '
git checkout -b branch2 A1 &&
touch g &&
git add g &&