Skip to content

Commit f67336d

Browse files
dschogitster
authored andcommitted
t3427: accommodate for the rebase --merge backend having been replaced
Since 68aa495 (rebase: implement --merge via the interactive machinery, 2018-12-11), the job of the old `--merge` backend is now performed by the `--interactive` backend, too. One consequence is that empty commits are no longer rebased by default. Meaning that the test case that calls `git rebase -Xsubtree` (which used to be handled by the `--merge` backend) now needs to ask explicitly for the empty commit to be rebased. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
1 parent a9c7107 commit f67336d

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

t/t3427-rebase-subtree.sh

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -83,10 +83,10 @@ test_expect_failure REBASE_P 'Rebase -Xsubtree --keep-empty --preserve-merges --
8383
'
8484

8585
# FAILURE: fatal: Could not parse object
86-
test_expect_failure 'Rebase -Xsubtree --onto commit' '
86+
test_expect_failure 'Rebase -Xsubtree --keep-empty --onto commit' '
8787
reset_rebase &&
8888
git checkout -b rebase-onto to-rebase &&
89-
git rebase -Xsubtree=files_subtree --onto files-master master &&
89+
git rebase -Xsubtree=files_subtree --keep-empty --onto files-master master &&
9090
verbose test "$(commit_message HEAD~2)" = "master4" &&
9191
verbose test "$(commit_message HEAD~)" = "files_subtree/master5" &&
9292
verbose test "$(commit_message HEAD)" = "Empty commit"

0 commit comments

Comments
 (0)