2013-06-07 08:11:37 +02:00
|
|
|
#!/bin/sh
|
|
|
|
|
|
|
|
test_description='basic rebase topology tests'
|
|
|
|
. ./test-lib.sh
|
|
|
|
. "$TEST_DIRECTORY"/lib-rebase.sh
|
|
|
|
|
|
|
|
# a---b---c
|
|
|
|
# \
|
|
|
|
# d---e
|
|
|
|
test_expect_success 'setup' '
|
|
|
|
test_commit a &&
|
|
|
|
test_commit b &&
|
|
|
|
test_commit c &&
|
|
|
|
git checkout b &&
|
|
|
|
test_commit d &&
|
|
|
|
test_commit e
|
|
|
|
'
|
|
|
|
|
|
|
|
test_run_rebase () {
|
|
|
|
result=$1
|
|
|
|
shift
|
|
|
|
test_expect_$result "simple rebase $*" "
|
|
|
|
reset_rebase &&
|
|
|
|
git rebase $* c e &&
|
|
|
|
test_cmp_rev c HEAD~2 &&
|
|
|
|
test_linear_range 'd e' c..
|
|
|
|
"
|
|
|
|
}
|
|
|
|
test_run_rebase success ''
|
|
|
|
test_run_rebase success -m
|
|
|
|
test_run_rebase success -i
|
2018-10-31 21:02:02 +01:00
|
|
|
test_have_prereq !REBASE_P || test_run_rebase success -p
|
2013-06-07 08:11:37 +02:00
|
|
|
|
|
|
|
test_run_rebase () {
|
|
|
|
result=$1
|
|
|
|
shift
|
|
|
|
test_expect_$result "rebase $* is no-op if upstream is an ancestor" "
|
|
|
|
reset_rebase &&
|
|
|
|
git rebase $* b e &&
|
|
|
|
test_cmp_rev e HEAD
|
|
|
|
"
|
|
|
|
}
|
|
|
|
test_run_rebase success ''
|
|
|
|
test_run_rebase success -m
|
|
|
|
test_run_rebase success -i
|
2018-10-31 21:02:02 +01:00
|
|
|
test_have_prereq !REBASE_P || test_run_rebase success -p
|
2013-06-07 08:11:37 +02:00
|
|
|
|
|
|
|
test_run_rebase () {
|
|
|
|
result=$1
|
|
|
|
shift
|
|
|
|
test_expect_$result "rebase $* -f rewrites even if upstream is an ancestor" "
|
|
|
|
reset_rebase &&
|
|
|
|
git rebase $* -f b e &&
|
|
|
|
! test_cmp_rev e HEAD &&
|
|
|
|
test_cmp_rev b HEAD~2 &&
|
|
|
|
test_linear_range 'd e' b..
|
|
|
|
"
|
|
|
|
}
|
|
|
|
test_run_rebase success ''
|
|
|
|
test_run_rebase success -m
|
|
|
|
test_run_rebase success -i
|
2018-10-31 21:02:02 +01:00
|
|
|
test_have_prereq !REBASE_P || test_run_rebase failure -p
|
2013-06-07 08:11:37 +02:00
|
|
|
|
|
|
|
test_run_rebase () {
|
|
|
|
result=$1
|
|
|
|
shift
|
|
|
|
test_expect_$result "rebase $* fast-forwards from ancestor of upstream" "
|
|
|
|
reset_rebase &&
|
|
|
|
git rebase $* e b &&
|
|
|
|
test_cmp_rev e HEAD
|
|
|
|
"
|
|
|
|
}
|
|
|
|
test_run_rebase success ''
|
|
|
|
test_run_rebase success -m
|
|
|
|
test_run_rebase success -i
|
2018-10-31 21:02:02 +01:00
|
|
|
test_have_prereq !REBASE_P || test_run_rebase success -p
|
2013-06-07 08:11:37 +02:00
|
|
|
|
2013-06-07 08:11:38 +02:00
|
|
|
# f
|
|
|
|
# /
|
|
|
|
# a---b---c---g---h
|
|
|
|
# \
|
2013-06-18 09:28:07 +02:00
|
|
|
# d---gp--i
|
2013-06-07 08:11:38 +02:00
|
|
|
#
|
2013-06-18 09:28:07 +02:00
|
|
|
# gp = cherry-picked g
|
2013-06-07 08:11:38 +02:00
|
|
|
# h = reverted g
|
|
|
|
#
|
|
|
|
# Reverted patches are there for tests to be able to check if a commit
|
|
|
|
# that introduced the same change as another commit is
|
|
|
|
# dropped. Without reverted commits, we could get false positives
|
|
|
|
# because applying the patch succeeds, but simply results in no
|
|
|
|
# changes.
|
|
|
|
test_expect_success 'setup of linear history for range selection tests' '
|
|
|
|
git checkout c &&
|
|
|
|
test_commit g &&
|
|
|
|
revert h g &&
|
|
|
|
git checkout d &&
|
2013-06-18 09:28:07 +02:00
|
|
|
cherry_pick gp g &&
|
2013-06-07 08:11:38 +02:00
|
|
|
test_commit i &&
|
|
|
|
git checkout b &&
|
|
|
|
test_commit f
|
|
|
|
'
|
|
|
|
|
|
|
|
test_run_rebase () {
|
|
|
|
result=$1
|
|
|
|
shift
|
|
|
|
test_expect_$result "rebase $* drops patches in upstream" "
|
|
|
|
reset_rebase &&
|
|
|
|
git rebase $* h i &&
|
|
|
|
test_cmp_rev h HEAD~2 &&
|
|
|
|
test_linear_range 'd i' h..
|
|
|
|
"
|
|
|
|
}
|
|
|
|
test_run_rebase success ''
|
rebase: implement --merge via the interactive machinery
As part of an ongoing effort to make rebase have more uniform behavior,
modify the merge backend to behave like the interactive one, by
re-implementing it on top of the latter.
Interactive rebases are implemented in terms of cherry-pick rather than
the merge-recursive builtin, but cherry-pick also calls into the
recursive merge machinery by default and can accept special merge
strategies and/or special strategy options. As such, there really is
not any need for having both git-rebase--merge and
git-rebase--interactive anymore. Delete git-rebase--merge.sh and
instead implement it in builtin/rebase.c.
This results in a few deliberate but small user-visible changes:
* The progress output is modified (see t3406 and t3420 for examples)
* A few known test failures are now fixed (see t3421)
* bash-prompt during a rebase --merge is now REBASE-i instead of
REBASE-m. Reason: The prompt is a reflection of the backend in use;
this allows users to report an issue to the git mailing list with
the appropriate backend information, and allows advanced users to
know where to search for relevant control files. (see t9903)
testcase modification notes:
t3406: --interactive and --merge had slightly different progress output
while running; adjust a test to match the new expectation
t3420: these test precise output while running, but rebase--am,
rebase--merge, and rebase--interactive all were built on very
different commands (am, merge-recursive, cherry-pick), so the
tests expected different output for each type. Now we expect
--merge and --interactive to have the same output.
t3421: --interactive fixes some bugs in --merge! Wahoo!
t9903: --merge uses the interactive backend so the prompt expected is
now REBASE-i.
Signed-off-by: Elijah Newren <newren@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2018-12-11 17:11:39 +01:00
|
|
|
test_run_rebase success -m
|
2013-06-07 08:11:38 +02:00
|
|
|
test_run_rebase success -i
|
2018-10-31 21:02:02 +01:00
|
|
|
test_have_prereq !REBASE_P || test_run_rebase success -p
|
2013-06-07 08:11:38 +02:00
|
|
|
|
|
|
|
test_run_rebase () {
|
|
|
|
result=$1
|
|
|
|
shift
|
|
|
|
test_expect_$result "rebase $* can drop last patch if in upstream" "
|
|
|
|
reset_rebase &&
|
2013-06-18 09:28:07 +02:00
|
|
|
git rebase $* h gp &&
|
2013-06-07 08:11:38 +02:00
|
|
|
test_cmp_rev h HEAD^ &&
|
|
|
|
test_linear_range 'd' h..
|
|
|
|
"
|
|
|
|
}
|
|
|
|
test_run_rebase success ''
|
rebase: implement --merge via the interactive machinery
As part of an ongoing effort to make rebase have more uniform behavior,
modify the merge backend to behave like the interactive one, by
re-implementing it on top of the latter.
Interactive rebases are implemented in terms of cherry-pick rather than
the merge-recursive builtin, but cherry-pick also calls into the
recursive merge machinery by default and can accept special merge
strategies and/or special strategy options. As such, there really is
not any need for having both git-rebase--merge and
git-rebase--interactive anymore. Delete git-rebase--merge.sh and
instead implement it in builtin/rebase.c.
This results in a few deliberate but small user-visible changes:
* The progress output is modified (see t3406 and t3420 for examples)
* A few known test failures are now fixed (see t3421)
* bash-prompt during a rebase --merge is now REBASE-i instead of
REBASE-m. Reason: The prompt is a reflection of the backend in use;
this allows users to report an issue to the git mailing list with
the appropriate backend information, and allows advanced users to
know where to search for relevant control files. (see t9903)
testcase modification notes:
t3406: --interactive and --merge had slightly different progress output
while running; adjust a test to match the new expectation
t3420: these test precise output while running, but rebase--am,
rebase--merge, and rebase--interactive all were built on very
different commands (am, merge-recursive, cherry-pick), so the
tests expected different output for each type. Now we expect
--merge and --interactive to have the same output.
t3421: --interactive fixes some bugs in --merge! Wahoo!
t9903: --merge uses the interactive backend so the prompt expected is
now REBASE-i.
Signed-off-by: Elijah Newren <newren@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2018-12-11 17:11:39 +01:00
|
|
|
test_run_rebase success -m
|
2013-06-07 08:11:38 +02:00
|
|
|
test_run_rebase success -i
|
2018-10-31 21:02:02 +01:00
|
|
|
test_have_prereq !REBASE_P || test_run_rebase success -p
|
2013-06-07 08:11:38 +02:00
|
|
|
|
|
|
|
test_run_rebase () {
|
|
|
|
result=$1
|
|
|
|
shift
|
|
|
|
test_expect_$result "rebase $* --onto drops patches in upstream" "
|
|
|
|
reset_rebase &&
|
|
|
|
git rebase $* --onto f h i &&
|
|
|
|
test_cmp_rev f HEAD~2 &&
|
|
|
|
test_linear_range 'd i' f..
|
|
|
|
"
|
|
|
|
}
|
|
|
|
test_run_rebase success ''
|
rebase: implement --merge via the interactive machinery
As part of an ongoing effort to make rebase have more uniform behavior,
modify the merge backend to behave like the interactive one, by
re-implementing it on top of the latter.
Interactive rebases are implemented in terms of cherry-pick rather than
the merge-recursive builtin, but cherry-pick also calls into the
recursive merge machinery by default and can accept special merge
strategies and/or special strategy options. As such, there really is
not any need for having both git-rebase--merge and
git-rebase--interactive anymore. Delete git-rebase--merge.sh and
instead implement it in builtin/rebase.c.
This results in a few deliberate but small user-visible changes:
* The progress output is modified (see t3406 and t3420 for examples)
* A few known test failures are now fixed (see t3421)
* bash-prompt during a rebase --merge is now REBASE-i instead of
REBASE-m. Reason: The prompt is a reflection of the backend in use;
this allows users to report an issue to the git mailing list with
the appropriate backend information, and allows advanced users to
know where to search for relevant control files. (see t9903)
testcase modification notes:
t3406: --interactive and --merge had slightly different progress output
while running; adjust a test to match the new expectation
t3420: these test precise output while running, but rebase--am,
rebase--merge, and rebase--interactive all were built on very
different commands (am, merge-recursive, cherry-pick), so the
tests expected different output for each type. Now we expect
--merge and --interactive to have the same output.
t3421: --interactive fixes some bugs in --merge! Wahoo!
t9903: --merge uses the interactive backend so the prompt expected is
now REBASE-i.
Signed-off-by: Elijah Newren <newren@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2018-12-11 17:11:39 +01:00
|
|
|
test_run_rebase success -m
|
2013-06-07 08:11:38 +02:00
|
|
|
test_run_rebase success -i
|
2018-10-31 21:02:02 +01:00
|
|
|
test_have_prereq !REBASE_P || test_run_rebase success -p
|
2013-06-07 08:11:38 +02:00
|
|
|
|
|
|
|
test_run_rebase () {
|
|
|
|
result=$1
|
|
|
|
shift
|
|
|
|
test_expect_$result "rebase $* --onto does not drop patches in onto" "
|
|
|
|
reset_rebase &&
|
|
|
|
git rebase $* --onto h f i &&
|
|
|
|
test_cmp_rev h HEAD~3 &&
|
2013-06-18 09:28:07 +02:00
|
|
|
test_linear_range 'd gp i' h..
|
2013-06-07 08:11:38 +02:00
|
|
|
"
|
|
|
|
}
|
|
|
|
test_run_rebase success ''
|
|
|
|
test_run_rebase success -m
|
|
|
|
test_run_rebase success -i
|
2018-10-31 21:02:02 +01:00
|
|
|
test_have_prereq !REBASE_P || test_run_rebase success -p
|
2013-06-07 08:11:38 +02:00
|
|
|
|
2013-06-07 08:11:39 +02:00
|
|
|
# a---b---c---j!
|
|
|
|
# \
|
|
|
|
# d---k!--l
|
|
|
|
#
|
|
|
|
# ! = empty
|
|
|
|
test_expect_success 'setup of linear history for empty commit tests' '
|
|
|
|
git checkout c &&
|
|
|
|
make_empty j &&
|
|
|
|
git checkout d &&
|
|
|
|
make_empty k &&
|
|
|
|
test_commit l
|
|
|
|
'
|
|
|
|
|
|
|
|
test_run_rebase () {
|
|
|
|
result=$1
|
|
|
|
shift
|
|
|
|
test_expect_$result "rebase $* drops empty commit" "
|
|
|
|
reset_rebase &&
|
|
|
|
git rebase $* c l &&
|
|
|
|
test_cmp_rev c HEAD~2 &&
|
|
|
|
test_linear_range 'd l' c..
|
|
|
|
"
|
|
|
|
}
|
|
|
|
test_run_rebase success ''
|
|
|
|
test_run_rebase success -m
|
|
|
|
test_run_rebase success -i
|
2018-10-31 21:02:02 +01:00
|
|
|
test_have_prereq !REBASE_P || test_run_rebase success -p
|
2013-06-07 08:11:39 +02:00
|
|
|
|
|
|
|
test_run_rebase () {
|
|
|
|
result=$1
|
|
|
|
shift
|
|
|
|
test_expect_$result "rebase $* --keep-empty" "
|
|
|
|
reset_rebase &&
|
|
|
|
git rebase $* --keep-empty c l &&
|
|
|
|
test_cmp_rev c HEAD~3 &&
|
|
|
|
test_linear_range 'd k l' c..
|
|
|
|
"
|
|
|
|
}
|
|
|
|
test_run_rebase success ''
|
2018-03-20 12:10:57 +01:00
|
|
|
test_run_rebase success -m
|
2013-06-07 08:11:39 +02:00
|
|
|
test_run_rebase success -i
|
2018-10-31 21:02:02 +01:00
|
|
|
test_have_prereq !REBASE_P || test_run_rebase failure -p
|
2013-06-07 08:11:39 +02:00
|
|
|
|
|
|
|
test_run_rebase () {
|
|
|
|
result=$1
|
|
|
|
shift
|
|
|
|
test_expect_$result "rebase $* --keep-empty keeps empty even if already in upstream" "
|
|
|
|
reset_rebase &&
|
|
|
|
git rebase $* --keep-empty j l &&
|
|
|
|
test_cmp_rev j HEAD~3 &&
|
|
|
|
test_linear_range 'd k l' j..
|
|
|
|
"
|
|
|
|
}
|
|
|
|
test_run_rebase success ''
|
2018-03-20 12:10:57 +01:00
|
|
|
test_run_rebase success -m
|
2018-03-20 11:03:14 +01:00
|
|
|
test_run_rebase success -i
|
2018-10-31 21:02:02 +01:00
|
|
|
test_have_prereq !REBASE_P || test_run_rebase failure -p
|
2018-04-25 14:29:14 +02:00
|
|
|
test_run_rebase success --rebase-merges
|
2013-06-07 08:11:39 +02:00
|
|
|
|
2013-06-07 08:11:40 +02:00
|
|
|
# m
|
|
|
|
# /
|
|
|
|
# a---b---c---g
|
|
|
|
#
|
2013-06-18 09:28:07 +02:00
|
|
|
# x---y---bp
|
2013-06-07 08:11:40 +02:00
|
|
|
#
|
2013-06-18 09:28:07 +02:00
|
|
|
# bp = cherry-picked b
|
2013-06-07 08:11:40 +02:00
|
|
|
# m = reverted b
|
|
|
|
#
|
|
|
|
# Reverted patches are there for tests to be able to check if a commit
|
|
|
|
# that introduced the same change as another commit is
|
|
|
|
# dropped. Without reverted commits, we could get false positives
|
|
|
|
# because applying the patch succeeds, but simply results in no
|
|
|
|
# changes.
|
|
|
|
test_expect_success 'setup of linear history for test involving root' '
|
|
|
|
git checkout b &&
|
|
|
|
revert m b &&
|
|
|
|
git checkout --orphan disjoint &&
|
|
|
|
git rm -rf . &&
|
|
|
|
test_commit x &&
|
|
|
|
test_commit y &&
|
2013-06-18 09:28:07 +02:00
|
|
|
cherry_pick bp b
|
2013-06-07 08:11:40 +02:00
|
|
|
'
|
|
|
|
|
|
|
|
test_run_rebase () {
|
|
|
|
result=$1
|
|
|
|
shift
|
|
|
|
test_expect_$result "rebase $* --onto --root" "
|
|
|
|
reset_rebase &&
|
|
|
|
git rebase $* --onto c --root y &&
|
|
|
|
test_cmp_rev c HEAD~2 &&
|
|
|
|
test_linear_range 'x y' c..
|
|
|
|
"
|
|
|
|
}
|
|
|
|
test_run_rebase success ''
|
2016-04-20 20:20:56 +02:00
|
|
|
test_run_rebase success -m
|
2013-06-07 08:11:40 +02:00
|
|
|
test_run_rebase success -i
|
2018-10-31 21:02:02 +01:00
|
|
|
test_have_prereq !REBASE_P || test_run_rebase success -p
|
2013-06-07 08:11:40 +02:00
|
|
|
|
|
|
|
test_run_rebase () {
|
|
|
|
result=$1
|
|
|
|
shift
|
|
|
|
test_expect_$result "rebase $* without --onto --root with disjoint history" "
|
|
|
|
reset_rebase &&
|
|
|
|
git rebase $* c y &&
|
|
|
|
test_cmp_rev c HEAD~2 &&
|
|
|
|
test_linear_range 'x y' c..
|
|
|
|
"
|
|
|
|
}
|
|
|
|
test_run_rebase success ''
|
2016-04-20 20:20:56 +02:00
|
|
|
test_run_rebase success -m
|
2013-06-07 08:11:40 +02:00
|
|
|
test_run_rebase success -i
|
2018-10-31 21:02:02 +01:00
|
|
|
test_have_prereq !REBASE_P || test_run_rebase failure -p
|
2013-06-07 08:11:40 +02:00
|
|
|
|
|
|
|
test_run_rebase () {
|
|
|
|
result=$1
|
|
|
|
shift
|
|
|
|
test_expect_$result "rebase $* --onto --root drops patch in onto" "
|
|
|
|
reset_rebase &&
|
2013-06-18 09:28:07 +02:00
|
|
|
git rebase $* --onto m --root bp &&
|
2013-06-07 08:11:40 +02:00
|
|
|
test_cmp_rev m HEAD~2 &&
|
|
|
|
test_linear_range 'x y' m..
|
|
|
|
"
|
|
|
|
}
|
|
|
|
test_run_rebase success ''
|
rebase: implement --merge via the interactive machinery
As part of an ongoing effort to make rebase have more uniform behavior,
modify the merge backend to behave like the interactive one, by
re-implementing it on top of the latter.
Interactive rebases are implemented in terms of cherry-pick rather than
the merge-recursive builtin, but cherry-pick also calls into the
recursive merge machinery by default and can accept special merge
strategies and/or special strategy options. As such, there really is
not any need for having both git-rebase--merge and
git-rebase--interactive anymore. Delete git-rebase--merge.sh and
instead implement it in builtin/rebase.c.
This results in a few deliberate but small user-visible changes:
* The progress output is modified (see t3406 and t3420 for examples)
* A few known test failures are now fixed (see t3421)
* bash-prompt during a rebase --merge is now REBASE-i instead of
REBASE-m. Reason: The prompt is a reflection of the backend in use;
this allows users to report an issue to the git mailing list with
the appropriate backend information, and allows advanced users to
know where to search for relevant control files. (see t9903)
testcase modification notes:
t3406: --interactive and --merge had slightly different progress output
while running; adjust a test to match the new expectation
t3420: these test precise output while running, but rebase--am,
rebase--merge, and rebase--interactive all were built on very
different commands (am, merge-recursive, cherry-pick), so the
tests expected different output for each type. Now we expect
--merge and --interactive to have the same output.
t3421: --interactive fixes some bugs in --merge! Wahoo!
t9903: --merge uses the interactive backend so the prompt expected is
now REBASE-i.
Signed-off-by: Elijah Newren <newren@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2018-12-11 17:11:39 +01:00
|
|
|
test_run_rebase success -m
|
2013-06-07 08:11:40 +02:00
|
|
|
test_run_rebase success -i
|
2018-10-31 21:02:02 +01:00
|
|
|
test_have_prereq !REBASE_P || test_run_rebase success -p
|
2013-06-07 08:11:40 +02:00
|
|
|
|
|
|
|
test_run_rebase () {
|
|
|
|
result=$1
|
|
|
|
shift
|
|
|
|
test_expect_$result "rebase $* --onto --root with merge-base does not go to root" "
|
|
|
|
reset_rebase &&
|
|
|
|
git rebase $* --onto m --root g &&
|
|
|
|
test_cmp_rev m HEAD~2 &&
|
|
|
|
test_linear_range 'c g' m..
|
|
|
|
"
|
|
|
|
}
|
|
|
|
|
|
|
|
test_run_rebase success ''
|
|
|
|
test_run_rebase success -m
|
|
|
|
test_run_rebase success -i
|
2018-10-31 21:02:02 +01:00
|
|
|
test_have_prereq !REBASE_P || test_run_rebase failure -p
|
2013-06-07 08:11:40 +02:00
|
|
|
|
|
|
|
test_run_rebase () {
|
|
|
|
result=$1
|
|
|
|
shift
|
|
|
|
test_expect_$result "rebase $* without --onto --root with disjoint history drops patch in onto" "
|
|
|
|
reset_rebase &&
|
2013-06-18 09:28:07 +02:00
|
|
|
git rebase $* m bp &&
|
2013-06-07 08:11:40 +02:00
|
|
|
test_cmp_rev m HEAD~2 &&
|
|
|
|
test_linear_range 'x y' m..
|
|
|
|
"
|
|
|
|
}
|
|
|
|
test_run_rebase success ''
|
rebase: implement --merge via the interactive machinery
As part of an ongoing effort to make rebase have more uniform behavior,
modify the merge backend to behave like the interactive one, by
re-implementing it on top of the latter.
Interactive rebases are implemented in terms of cherry-pick rather than
the merge-recursive builtin, but cherry-pick also calls into the
recursive merge machinery by default and can accept special merge
strategies and/or special strategy options. As such, there really is
not any need for having both git-rebase--merge and
git-rebase--interactive anymore. Delete git-rebase--merge.sh and
instead implement it in builtin/rebase.c.
This results in a few deliberate but small user-visible changes:
* The progress output is modified (see t3406 and t3420 for examples)
* A few known test failures are now fixed (see t3421)
* bash-prompt during a rebase --merge is now REBASE-i instead of
REBASE-m. Reason: The prompt is a reflection of the backend in use;
this allows users to report an issue to the git mailing list with
the appropriate backend information, and allows advanced users to
know where to search for relevant control files. (see t9903)
testcase modification notes:
t3406: --interactive and --merge had slightly different progress output
while running; adjust a test to match the new expectation
t3420: these test precise output while running, but rebase--am,
rebase--merge, and rebase--interactive all were built on very
different commands (am, merge-recursive, cherry-pick), so the
tests expected different output for each type. Now we expect
--merge and --interactive to have the same output.
t3421: --interactive fixes some bugs in --merge! Wahoo!
t9903: --merge uses the interactive backend so the prompt expected is
now REBASE-i.
Signed-off-by: Elijah Newren <newren@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2018-12-11 17:11:39 +01:00
|
|
|
test_run_rebase success -m
|
2013-06-07 08:11:40 +02:00
|
|
|
test_run_rebase success -i
|
2018-10-31 21:02:02 +01:00
|
|
|
test_have_prereq !REBASE_P || test_run_rebase failure -p
|
2013-06-07 08:11:40 +02:00
|
|
|
|
|
|
|
test_run_rebase () {
|
|
|
|
result=$1
|
|
|
|
shift
|
|
|
|
test_expect_$result "rebase $* --root on linear history is a no-op" "
|
|
|
|
reset_rebase &&
|
|
|
|
git rebase $* --root c &&
|
|
|
|
test_cmp_rev c HEAD
|
|
|
|
"
|
|
|
|
}
|
rebase -i --root: let the sequencer handle even the initial part
In this developer's earlier attempt to accelerate interactive rebases by
converting large parts from Unix shell script into portable, performant
C, the --root handling was specifically excluded (to simplify the task a
little bit; it still took over a year to get that reduced set of patches
into Git proper).
This patch ties up that loose end: now only --preserve-merges uses the
slow Unix shell script implementation to perform the interactive rebase.
As the rebase--helper reports progress to stderr (unlike the scripted
interactive rebase, which reports it to stdout, of all places), we have
to adjust a couple of tests that did not expect that for `git rebase -i
--root`.
This patch fixes -- at long last! -- the really old bug reported in
6a6bc5bdc4d (add tests for rebasing root, 2013-06-06) that rebasing with
--root *always* rewrote the root commit, even if there were no changes.
The bug still persists in --preserve-merges mode, of course, but that
mode will be deprecated as soon as the new --rebase-merges mode
stabilizes, anyway.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2018-05-04 01:01:18 +02:00
|
|
|
test_run_rebase success ''
|
|
|
|
test_run_rebase success -m
|
|
|
|
test_run_rebase success -i
|
2018-10-31 21:02:02 +01:00
|
|
|
test_have_prereq !REBASE_P || test_run_rebase failure -p
|
2013-06-07 08:11:40 +02:00
|
|
|
|
|
|
|
test_run_rebase () {
|
|
|
|
result=$1
|
|
|
|
shift
|
|
|
|
test_expect_$result "rebase $* -f --root on linear history causes re-write" "
|
|
|
|
reset_rebase &&
|
|
|
|
git rebase $* -f --root c &&
|
|
|
|
! test_cmp_rev a HEAD~2 &&
|
|
|
|
test_linear_range 'a b c' HEAD
|
|
|
|
"
|
|
|
|
}
|
|
|
|
test_run_rebase success ''
|
|
|
|
test_run_rebase success -m
|
|
|
|
test_run_rebase success -i
|
2018-10-31 21:02:02 +01:00
|
|
|
test_have_prereq !REBASE_P || test_run_rebase success -p
|
2013-06-07 08:11:40 +02:00
|
|
|
|
2013-06-07 08:11:37 +02:00
|
|
|
test_done
|