2019-08-18 02:41:24 +08:00
|
|
|
#!/bin/sh
|
|
|
|
|
|
|
|
test_description='recursive merge diff3 style conflict markers'
|
|
|
|
|
|
|
|
. ./test-lib.sh
|
|
|
|
|
|
|
|
# Setup:
|
|
|
|
# L1
|
|
|
|
# \
|
|
|
|
# ?
|
|
|
|
# /
|
|
|
|
# R1
|
|
|
|
#
|
|
|
|
# Where:
|
|
|
|
# L1 and R1 both have a file named 'content' but have no common history
|
|
|
|
#
|
|
|
|
|
|
|
|
test_expect_success 'setup no merge base' '
|
|
|
|
test_create_repo no_merge_base &&
|
|
|
|
(
|
|
|
|
cd no_merge_base &&
|
|
|
|
|
|
|
|
git checkout -b L &&
|
|
|
|
test_commit A content A &&
|
|
|
|
|
|
|
|
git checkout --orphan R &&
|
|
|
|
test_commit B content B
|
|
|
|
)
|
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'check no merge base' '
|
|
|
|
(
|
|
|
|
cd no_merge_base &&
|
|
|
|
|
|
|
|
git checkout L^0 &&
|
|
|
|
|
|
|
|
test_must_fail git -c merge.conflictstyle=diff3 merge --allow-unrelated-histories -s recursive R^0 &&
|
|
|
|
|
|
|
|
grep "|||||| empty tree" content
|
|
|
|
)
|
|
|
|
'
|
|
|
|
|
|
|
|
# Setup:
|
|
|
|
# L1
|
|
|
|
# / \
|
|
|
|
# master ?
|
|
|
|
# \ /
|
|
|
|
# R1
|
|
|
|
#
|
|
|
|
# Where:
|
|
|
|
# L1 and R1 have modified the same file ('content') in conflicting ways
|
|
|
|
#
|
|
|
|
|
|
|
|
test_expect_success 'setup unique merge base' '
|
|
|
|
test_create_repo unique_merge_base &&
|
|
|
|
(
|
|
|
|
cd unique_merge_base &&
|
|
|
|
|
|
|
|
test_commit base content "1
|
|
|
|
2
|
|
|
|
3
|
|
|
|
4
|
|
|
|
5
|
|
|
|
" &&
|
|
|
|
|
|
|
|
git branch L &&
|
|
|
|
git branch R &&
|
|
|
|
|
|
|
|
git checkout L &&
|
|
|
|
test_commit L content "1
|
|
|
|
2
|
|
|
|
3
|
|
|
|
4
|
|
|
|
5
|
|
|
|
7" &&
|
|
|
|
|
|
|
|
git checkout R &&
|
|
|
|
git rm content &&
|
|
|
|
test_commit R renamed "1
|
|
|
|
2
|
|
|
|
3
|
|
|
|
4
|
|
|
|
5
|
|
|
|
six"
|
|
|
|
)
|
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'check unique merge base' '
|
|
|
|
(
|
|
|
|
cd unique_merge_base &&
|
|
|
|
|
|
|
|
git checkout L^0 &&
|
|
|
|
MASTER=$(git rev-parse --short master) &&
|
|
|
|
|
|
|
|
test_must_fail git -c merge.conflictstyle=diff3 merge -s recursive R^0 &&
|
|
|
|
|
|
|
|
grep "|||||| $MASTER:content" renamed
|
|
|
|
)
|
|
|
|
'
|
|
|
|
|
|
|
|
# Setup:
|
|
|
|
# L1---L2--L3
|
|
|
|
# / \ / \
|
|
|
|
# master X1 ?
|
|
|
|
# \ / \ /
|
|
|
|
# R1---R2--R3
|
|
|
|
#
|
|
|
|
# Where:
|
|
|
|
# commits L1 and R1 have modified the same file in non-conflicting ways
|
|
|
|
# X1 is an auto-generated merge-base used when merging L1 and R1
|
|
|
|
# commits L2 and R2 are merges of R1 and L1 into L1 and R1, respectively
|
|
|
|
# commits L3 and R3 both modify 'content' in conflicting ways
|
|
|
|
#
|
|
|
|
|
|
|
|
test_expect_success 'setup multiple merge bases' '
|
|
|
|
test_create_repo multiple_merge_bases &&
|
|
|
|
(
|
|
|
|
cd multiple_merge_bases &&
|
|
|
|
|
|
|
|
test_commit initial content "1
|
|
|
|
2
|
|
|
|
3
|
|
|
|
4
|
|
|
|
5" &&
|
|
|
|
|
|
|
|
git branch L &&
|
|
|
|
git branch R &&
|
|
|
|
|
|
|
|
# Create L1
|
|
|
|
git checkout L &&
|
|
|
|
test_commit L1 content "0
|
|
|
|
1
|
|
|
|
2
|
|
|
|
3
|
|
|
|
4
|
|
|
|
5" &&
|
|
|
|
|
|
|
|
# Create R1
|
|
|
|
git checkout R &&
|
|
|
|
test_commit R1 content "1
|
|
|
|
2
|
|
|
|
3
|
|
|
|
4
|
|
|
|
5
|
|
|
|
6" &&
|
|
|
|
|
|
|
|
# Create L2
|
|
|
|
git checkout L &&
|
|
|
|
git merge R1 &&
|
|
|
|
|
|
|
|
# Create R2
|
|
|
|
git checkout R &&
|
|
|
|
git merge L1 &&
|
|
|
|
|
|
|
|
# Create L3
|
|
|
|
git checkout L &&
|
|
|
|
test_commit L3 content "0
|
|
|
|
1
|
|
|
|
2
|
|
|
|
3
|
|
|
|
4
|
|
|
|
5
|
|
|
|
A" &&
|
|
|
|
|
|
|
|
# Create R3
|
|
|
|
git checkout R &&
|
|
|
|
git rm content &&
|
|
|
|
test_commit R3 renamed "0
|
|
|
|
2
|
|
|
|
3
|
|
|
|
4
|
|
|
|
5
|
|
|
|
six"
|
|
|
|
)
|
|
|
|
'
|
|
|
|
|
|
|
|
test_expect_success 'check multiple merge bases' '
|
|
|
|
(
|
|
|
|
cd multiple_merge_bases &&
|
|
|
|
|
|
|
|
git checkout L^0 &&
|
|
|
|
|
|
|
|
test_must_fail git -c merge.conflictstyle=diff3 merge -s recursive R^0 &&
|
|
|
|
|
|
|
|
grep "|||||| merged common ancestors:content" renamed
|
|
|
|
)
|
|
|
|
'
|
|
|
|
|
2020-02-16 05:36:38 +08:00
|
|
|
test_expect_success 'rebase --merge describes parent of commit being picked' '
|
merge-recursive: fix the diff3 common ancestor label for virtual commits
In commit 743474cbfa8b ("merge-recursive: provide a better label for
diff3 common ancestor", 2019-08-17), the label for the common ancestor
was changed from always being
"merged common ancestors"
to instead be based on the number of merge bases:
>=2: "merged common ancestors"
1: <abbreviated commit hash>
0: "<empty tree>"
Unfortunately, this did not take into account that when we have a single
merge base, that merge base could be fake or constructed. In such
cases, this resulted in a label of "00000000". Of course, the previous
label of "merged common ancestors" was also misleading for this case.
Since we have an API that is explicitly about creating fake merge base
commits in merge_recursive_generic(), we should provide a better label
when using that API with one merge base. So, when
merge_recursive_generic() is called with one merge base, set the label
to:
"constructed merge base"
Note that callers of merge_recursive_generic() include the builtin
commands git-am (in combination with git apply --build-fake-ancestor),
git-merge-recursive, and git-stash.
Helped-by: Jeff King <peff@peff.net>
Signed-off-by: Elijah Newren <newren@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2019-10-02 02:17:27 +08:00
|
|
|
test_create_repo rebase &&
|
|
|
|
(
|
|
|
|
cd rebase &&
|
|
|
|
test_commit base file &&
|
|
|
|
test_commit master file &&
|
|
|
|
git checkout -b side HEAD^ &&
|
|
|
|
test_commit side file &&
|
2020-02-16 05:36:38 +08:00
|
|
|
test_must_fail git -c merge.conflictstyle=diff3 rebase --merge master &&
|
|
|
|
grep "||||||| parent of" file
|
|
|
|
)
|
|
|
|
'
|
|
|
|
|
2020-02-16 05:36:41 +08:00
|
|
|
test_expect_success 'rebase --apply describes fake ancestor base' '
|
2020-02-16 05:36:38 +08:00
|
|
|
(
|
|
|
|
cd rebase &&
|
|
|
|
git rebase --abort &&
|
2020-02-16 05:36:41 +08:00
|
|
|
test_must_fail git -c merge.conflictstyle=diff3 rebase --apply master &&
|
merge-recursive: fix the diff3 common ancestor label for virtual commits
In commit 743474cbfa8b ("merge-recursive: provide a better label for
diff3 common ancestor", 2019-08-17), the label for the common ancestor
was changed from always being
"merged common ancestors"
to instead be based on the number of merge bases:
>=2: "merged common ancestors"
1: <abbreviated commit hash>
0: "<empty tree>"
Unfortunately, this did not take into account that when we have a single
merge base, that merge base could be fake or constructed. In such
cases, this resulted in a label of "00000000". Of course, the previous
label of "merged common ancestors" was also misleading for this case.
Since we have an API that is explicitly about creating fake merge base
commits in merge_recursive_generic(), we should provide a better label
when using that API with one merge base. So, when
merge_recursive_generic() is called with one merge base, set the label
to:
"constructed merge base"
Note that callers of merge_recursive_generic() include the builtin
commands git-am (in combination with git apply --build-fake-ancestor),
git-merge-recursive, and git-stash.
Helped-by: Jeff King <peff@peff.net>
Signed-off-by: Elijah Newren <newren@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2019-10-02 02:17:27 +08:00
|
|
|
grep "||||||| constructed merge base" file
|
|
|
|
)
|
|
|
|
'
|
|
|
|
|
2019-08-18 02:41:24 +08:00
|
|
|
test_done
|