3 test_description
="recursive merge corner cases w/ renames but not criss-crosses"
4 # t6036 has corner cases that involve both criss-cross merges and renames
8 test_setup_rename_delete_untracked
() {
9 test_create_repo rename-delete-untracked
&&
11 cd rename-delete-untracked
&&
13 echo "A pretty inscription" >ring
&&
16 git commit
-m beginning
&&
19 git checkout
-b rename-the-ring
&&
20 git
mv ring one-ring-to-rule-them-all
&&
22 git commit
-m fullname
&&
24 git checkout people
&&
29 git commit
-m track-people-instead-of-objects
&&
30 echo "Myyy PRECIOUSSS" >ring
34 test_expect_success
"Does git preserve Gollum's precious artifact?" '
35 test_setup_rename_delete_untracked &&
37 cd rename-delete-untracked &&
39 test_must_fail git merge -s recursive rename-the-ring &&
41 # Make sure git did not delete an untracked file
42 test_path_is_file ring
46 # Testcase setup for rename/modify/add-source:
47 # Commit A: new file: a
48 # Commit B: modify a slightly
49 # Commit C: rename a->b, add completely different a
51 # We should be able to merge B & C cleanly
53 test_setup_rename_modify_add_source
() {
54 test_create_repo rename-modify-add-source
&&
56 cd rename-modify-add-source
&&
58 printf "1\n2\n3\n4\n5\n6\n7\n" >a
&&
63 git checkout
-b B A
&&
68 git checkout
-b C A
&&
70 echo something completely different
>a
&&
76 test_expect_failure
'rename/modify/add-source conflict resolvable' '
77 test_setup_rename_modify_add_source &&
79 cd rename-modify-add-source &&
83 git merge -s recursive C^0 &&
85 git rev-parse >expect \
87 git rev-parse >actual \
89 test_cmp expect actual
93 test_setup_break_detection_1
() {
94 test_create_repo break-detection-1
&&
96 cd break-detection-1
&&
98 printf "1\n2\n3\n4\n5\n" >a
&&
104 git checkout
-b B A
&&
106 echo "Completely different content" >a
&&
110 git checkout
-b C A
&&
117 test_expect_failure
'conflict caused if rename not detected' '
118 test_setup_break_detection_1 &&
120 cd break-detection-1 &&
122 git checkout -q C^0 &&
123 git merge -s recursive B^0 &&
125 git ls-files -s >out &&
126 test_line_count = 3 out &&
127 git ls-files -u >out &&
128 test_line_count = 0 out &&
129 git ls-files -o >out &&
130 test_line_count = 1 out &&
132 test_line_count = 6 c &&
133 git rev-parse >expect \
135 git rev-parse >actual \
137 test_cmp expect actual
141 test_setup_break_detection_2
() {
142 test_create_repo break-detection-2
&&
144 cd break-detection-2
&&
146 printf "1\n2\n3\n4\n5\n" >a
&&
152 git checkout
-b D A
&&
156 echo "Completely different content" >a
&&
160 git checkout
-b E A
&&
162 echo "Completely different content" >>a
&&
168 test_expect_failure
'missed conflict if rename not detected' '
169 test_setup_break_detection_2 &&
171 cd break-detection-2 &&
173 git checkout -q E^0 &&
174 test_must_fail git merge -s recursive D^0
178 # Tests for undetected rename/add-source causing a file to erroneously be
179 # deleted (and for mishandled rename/rename(1to1) causing the same issue).
181 # This test uses a rename/rename(1to1)+add-source conflict (1to1 means the
182 # same file is renamed on both sides to the same thing; it should trigger
183 # the 1to2 logic, which it would do if the add-source didn't cause issues
184 # for git's rename detection):
185 # Commit A: new file: a
186 # Commit B: rename a->b
187 # Commit C: rename a->b, add unrelated a
189 test_setup_break_detection_3
() {
190 test_create_repo break-detection-3
&&
192 cd break-detection-3
&&
194 printf "1\n2\n3\n4\n5\n" >a
&&
199 git checkout
-b B A
&&
203 git checkout
-b C A
&&
211 test_expect_failure
'detect rename/add-source and preserve all data' '
212 test_setup_break_detection_3 &&
214 cd break-detection-3 &&
218 git merge -s recursive C^0 &&
220 git ls-files -s >out &&
221 test_line_count = 2 out &&
222 git ls-files -u >out &&
223 test_line_count = 2 out &&
224 git ls-files -o >out &&
225 test_line_count = 1 out &&
227 test_path_is_file a &&
228 test_path_is_file b &&
230 git rev-parse >expect \
232 git rev-parse >actual \
234 test_cmp expect actual
238 test_expect_failure
'detect rename/add-source and preserve all data, merge other way' '
239 test_setup_break_detection_3 &&
241 cd break-detection-3 &&
245 git merge -s recursive B^0 &&
247 git ls-files -s >out &&
248 test_line_count = 2 out &&
249 git ls-files -u >out &&
250 test_line_count = 2 out &&
251 git ls-files -o >out &&
252 test_line_count = 1 out &&
254 test_path_is_file a &&
255 test_path_is_file b &&
257 git rev-parse >expect \
259 git rev-parse >actual \
261 test_cmp expect actual
265 test_setup_rename_directory
() {
266 test_create_repo rename-directory-
$1 &&
268 cd rename-directory-
$1 &&
270 printf "1\n2\n3\n4\n5\n6\n" >file &&
273 git commit
-m base
&&
276 git checkout
-b right
&&
279 echo junk
>newfile
/realfile
&&
280 git add
file newfile
/realfile
&&
282 git commit
-m right
&&
284 git checkout
-b left-conflict base
&&
287 git
mv file newfile
&&
289 git commit
-m left
&&
291 git checkout
-b left-clean base
&&
293 cat file >>newfile
&&
301 test_expect_success
'rename/directory conflict + clean content merge' '
302 test_setup_rename_directory 1a &&
304 cd rename-directory-1a &&
306 git checkout left-clean^0 &&
308 test_must_fail git merge -s recursive right^0 &&
310 git ls-files -s >out &&
311 test_line_count = 2 out &&
312 git ls-files -u >out &&
313 test_line_count = 1 out &&
314 git ls-files -o >out &&
315 test_line_count = 2 out &&
318 git cat-file -p base:file >>expect &&
320 test_cmp expect newfile~HEAD &&
322 test $(git rev-parse :2:newfile) = $(git hash-object expect) &&
324 test_path_is_file newfile/realfile &&
325 test_path_is_file newfile~HEAD
329 test_expect_success
'rename/directory conflict + content merge conflict' '
330 test_setup_rename_directory 1b &&
332 cd rename-directory-1b &&
337 git checkout left-conflict^0 &&
339 test_must_fail git merge -s recursive right^0 &&
341 git ls-files -s >out &&
342 test_line_count = 4 out &&
343 git ls-files -u >out &&
344 test_line_count = 3 out &&
345 git ls-files -o >out &&
346 test_line_count = 2 out &&
348 git cat-file -p left-conflict:newfile >left &&
349 git cat-file -p base:file >base &&
350 git cat-file -p right:file >right &&
351 test_must_fail git merge-file \
356 test_cmp left newfile~HEAD &&
358 git rev-parse >expect \
359 base:file left-conflict:newfile right:file &&
360 git rev-parse >actual \
361 :1:newfile :2:newfile :3:newfile &&
362 test_cmp expect actual &&
364 test_path_is_file newfile/realfile &&
365 test_path_is_file newfile~HEAD
369 test_setup_rename_directory_2
() {
370 test_create_repo rename-directory-2
&&
372 cd rename-directory-2
&&
375 printf "1\n2\n3\n4\n5\n6\n" >sub
/file &&
378 git commit
-m base
&&
381 git checkout
-b right
&&
385 git commit
-m right
&&
387 git checkout
-b left base
&&
389 cat sub
/file >>newfile
&&
398 test_expect_success
'disappearing dir in rename/directory conflict handled' '
399 test_setup_rename_directory_2 &&
401 cd rename-directory-2 &&
403 git checkout left^0 &&
405 git merge -s recursive right^0 &&
407 git ls-files -s >out &&
408 test_line_count = 1 out &&
409 git ls-files -u >out &&
410 test_line_count = 0 out &&
411 git ls-files -o >out &&
412 test_line_count = 1 out &&
415 git cat-file -p base:sub/file >>expect &&
417 test_cmp expect sub &&
419 test_path_is_file sub
423 # Test for basic rename/add-dest conflict, with rename needing content merge:
425 # Commit A: rename a->b, modifying b too
426 # Commit B: modify a, add different b
428 test_setup_rename_with_content_merge_and_add
() {
429 test_create_repo rename-with-content-merge-and-add-
$1 &&
431 cd rename-with-content-merge-and-add-
$1 &&
438 git checkout
-b A O
&&
444 git checkout
-b B O
&&
446 echo hello world
>b
&&
452 test_expect_success
'handle rename-with-content-merge vs. add' '
453 test_setup_rename_with_content_merge_and_add AB &&
455 cd rename-with-content-merge-and-add-AB &&
459 test_must_fail git merge -s recursive B^0 >out &&
460 test_i18ngrep "CONFLICT (.*/add)" out &&
462 git ls-files -s >out &&
463 test_line_count = 2 out &&
464 git ls-files -u >out &&
465 test_line_count = 2 out &&
466 # Also, make sure both unmerged entries are for "b"
467 git ls-files -u b >out &&
468 test_line_count = 2 out &&
469 git ls-files -o >out &&
470 test_line_count = 1 out &&
472 test_path_is_missing a &&
473 test_path_is_file b &&
476 git hash-object tmp >expect &&
477 git rev-parse B:b >>expect &&
478 git rev-parse >actual \
480 test_cmp expect actual &&
482 # Test that the two-way merge in b is as expected
483 git cat-file -p :2:b >>ours &&
484 git cat-file -p :3:b >>theirs &&
486 test_must_fail git merge-file \
495 test_expect_success
'handle rename-with-content-merge vs. add, merge other way' '
496 test_setup_rename_with_content_merge_and_add BA &&
498 cd rename-with-content-merge-and-add-BA &&
505 test_must_fail git merge -s recursive A^0 >out &&
506 test_i18ngrep "CONFLICT (.*/add)" out &&
508 git ls-files -s >out &&
509 test_line_count = 2 out &&
510 git ls-files -u >out &&
511 test_line_count = 2 out &&
512 # Also, make sure both unmerged entries are for "b"
513 git ls-files -u b >out &&
514 test_line_count = 2 out &&
515 git ls-files -o >out &&
516 test_line_count = 1 out &&
518 test_path_is_missing a &&
519 test_path_is_file b &&
522 git rev-parse B:b >expect &&
523 git hash-object tmp >>expect &&
524 git rev-parse >actual \
526 test_cmp expect actual &&
528 # Test that the two-way merge in b is as expected
529 git cat-file -p :2:b >>ours &&
530 git cat-file -p :3:b >>theirs &&
532 test_must_fail git merge-file \
541 # Test for all kinds of things that can go wrong with rename/rename (2to1):
542 # Commit A: new files: a & b
543 # Commit B: rename a->c, modify b
544 # Commit C: rename b->c, modify a
546 # Merging of B & C should NOT be clean. Questions:
547 # * Both a & b should be removed by the merge; are they?
548 # * The two c's should contain modifications to a & b; do they?
549 # * The index should contain two files, both for c; does it?
550 # * The working copy should have two files, both of form c~<unique>; does it?
551 # * Nothing else should be present. Is anything?
553 test_setup_rename_rename_2to1
() {
554 test_create_repo rename-rename-2to1
&&
556 cd rename-rename-2to1
&&
558 printf "1\n2\n3\n4\n5\n" >a
&&
559 printf "5\n4\n3\n2\n1\n" >b
&&
564 git checkout
-b B A
&&
570 git checkout
-b C A
&&
578 test_expect_success
'handle rename/rename (2to1) conflict correctly' '
579 test_setup_rename_rename_2to1 &&
581 cd rename-rename-2to1 &&
585 test_must_fail git merge -s recursive C^0 >out &&
586 test_i18ngrep "CONFLICT (\(.*\)/\1)" out &&
588 git ls-files -s >out &&
589 test_line_count = 2 out &&
590 git ls-files -u >out &&
591 test_line_count = 2 out &&
592 git ls-files -u c >out &&
593 test_line_count = 2 out &&
594 git ls-files -o >out &&
595 test_line_count = 1 out &&
597 test_path_is_missing a &&
598 test_path_is_missing b &&
600 git rev-parse >expect \
602 git rev-parse >actual \
604 test_cmp expect actual &&
606 # Test that the two-way merge in new_a is as expected
607 git cat-file -p :2:c >>ours &&
608 git cat-file -p :3:c >>theirs &&
610 test_must_fail git merge-file \
615 git hash-object c >actual &&
616 git hash-object ours >expect &&
617 test_cmp expect actual
621 # Testcase setup for simple rename/rename (1to2) conflict:
622 # Commit A: new file: a
623 # Commit B: rename a->b
624 # Commit C: rename a->c
625 test_setup_rename_rename_1to2
() {
626 test_create_repo rename-rename-1to2
&&
628 cd rename-rename-1to2
&&
636 git checkout
-b B A
&&
641 git checkout
-b C A
&&
648 test_expect_success
'merge has correct working tree contents' '
649 test_setup_rename_rename_1to2 &&
651 cd rename-rename-1to2 &&
655 test_must_fail git merge -s recursive B^0 &&
657 git ls-files -s >out &&
658 test_line_count = 3 out &&
659 git ls-files -u >out &&
660 test_line_count = 3 out &&
661 git ls-files -o >out &&
662 test_line_count = 1 out &&
664 test_path_is_missing a &&
665 git rev-parse >expect \
668 git rev-parse >actual \
670 git hash-object >>actual \
672 test_cmp expect actual
676 # Testcase setup for rename/rename(1to2)/add-source conflict:
677 # Commit A: new file: a
678 # Commit B: rename a->b
679 # Commit C: rename a->c, add completely different a
681 # Merging of B & C should NOT be clean; there's a rename/rename conflict
683 test_setup_rename_rename_1to2_add_source_1
() {
684 test_create_repo rename-rename-1to2-add-source-1
&&
686 cd rename-rename-1to2-add-source-1
&&
688 printf "1\n2\n3\n4\n5\n6\n7\n" >a
&&
693 git checkout
-b B A
&&
697 git checkout
-b C A
&&
699 echo something completely different
>a
&&
705 test_expect_failure
'detect conflict with rename/rename(1to2)/add-source merge' '
706 test_setup_rename_rename_1to2_add_source_1 &&
708 cd rename-rename-1to2-add-source-1 &&
712 test_must_fail git merge -s recursive C^0 &&
714 git ls-files -s >out &&
715 test_line_count = 4 out &&
716 git ls-files -o >out &&
717 test_line_count = 1 out &&
719 git rev-parse >expect \
721 git rev-parse >actual \
722 :3:a :1:a :2:b :3:c &&
723 test_cmp expect actual &&
725 test_path_is_file a &&
726 test_path_is_file b &&
731 test_setup_rename_rename_1to2_add_source_2
() {
732 test_create_repo rename-rename-1to2-add-source-2
&&
734 cd rename-rename-1to2-add-source-2
&&
739 git commit
-m base
&&
742 git checkout
-b B A
&&
747 git checkout
-b C A
&&
749 echo important-info
>a
&&
756 test_expect_failure
'rename/rename/add-source still tracks new a file' '
757 test_setup_rename_rename_1to2_add_source_2 &&
759 cd rename-rename-1to2-add-source-2 &&
762 git merge -s recursive B^0 &&
764 git ls-files -s >out &&
765 test_line_count = 2 out &&
766 git ls-files -o >out &&
767 test_line_count = 1 out &&
769 git rev-parse >expect \
771 git rev-parse >actual \
773 test_cmp expect actual
777 test_setup_rename_rename_1to2_add_dest
() {
778 test_create_repo rename-rename-1to2-add-dest
&&
780 cd rename-rename-1to2-add-dest
&&
785 git commit
-m base
&&
788 git checkout
-b B A
&&
790 echo precious-data
>c
&&
795 git checkout
-b C A
&&
797 echo important-info
>b
&&
804 test_expect_success
'rename/rename/add-dest merge still knows about conflicting file versions' '
805 test_setup_rename_rename_1to2_add_dest &&
807 cd rename-rename-1to2-add-dest &&
810 test_must_fail git merge -s recursive B^0 &&
812 git ls-files -s >out &&
813 test_line_count = 5 out &&
814 git ls-files -u b >out &&
815 test_line_count = 2 out &&
816 git ls-files -u c >out &&
817 test_line_count = 2 out &&
818 git ls-files -o >out &&
819 test_line_count = 1 out &&
821 git rev-parse >expect \
822 A:a C:b B:b C:c B:c &&
823 git rev-parse >actual \
824 :1:a :2:b :3:b :2:c :3:c &&
825 test_cmp expect actual &&
827 # Record some contents for re-doing merges
828 git cat-file -p A:a >stuff &&
829 git cat-file -p C:b >important_info &&
830 git cat-file -p B:c >precious_data &&
833 # Test the merge in b
834 test_must_fail git merge-file \
838 important_info empty stuff &&
839 test_cmp important_info b &&
841 # Test the merge in c
842 test_must_fail git merge-file \
846 stuff empty precious_data &&
851 # Testcase rad, rename/add/delete
853 # Commit A: rm foo, add different bar
854 # Commit B: rename foo->bar
855 # Expected: CONFLICT (rename/add/delete), two-way merged bar
858 test_create_repo rad
&&
861 echo "original file" >foo
&&
863 git commit
-m "original" &&
871 echo "different file" >bar
&&
873 git commit
-m "Remove foo, add bar" &&
877 git commit
-m "rename foo to bar"
881 test_expect_failure
'rad-check: rename/add/delete conflict' '
887 test_must_fail git merge -s recursive A^0 >out 2>err &&
889 # Instead of requiring the output to contain one combined line
890 # CONFLICT (rename/add/delete)
891 # or perhaps two lines:
892 # CONFLICT (rename/add): new file collides with rename target
893 # CONFLICT (rename/delete): rename source removed on other side
894 # and instead of requiring "rename/add" instead of "add/add",
895 # be flexible in the type of console output message(s) reported
896 # for this particular case; we will be more stringent about the
897 # contents of the index and working directory.
898 test_i18ngrep "CONFLICT (.*/add)" out &&
899 test_i18ngrep "CONFLICT (rename.*/delete)" out &&
900 test_must_be_empty err &&
902 git ls-files -s >file_count &&
903 test_line_count = 2 file_count &&
904 git ls-files -u >file_count &&
905 test_line_count = 2 file_count &&
906 git ls-files -o >file_count &&
907 test_line_count = 3 file_count &&
909 git rev-parse >actual \
911 git rev-parse >expect \
914 test_path_is_missing foo &&
915 # bar should have two-way merged contents of the different
916 # versions of bar; check that content from both sides is
923 # Testcase rrdd, rename/rename(2to1)/delete/delete
925 # Commit A: rename foo->baz, rm bar
926 # Commit B: rename bar->baz, rm foo
927 # Expected: CONFLICT (rename/rename/delete/delete), two-way merged baz
930 test_create_repo rrdd
&&
945 git commit
-m "Rename foo, remove bar" &&
950 git commit
-m "Rename bar, remove foo"
954 test_expect_failure
'rrdd-check: rename/rename(2to1)/delete/delete conflict' '
960 test_must_fail git merge -s recursive B^0 >out 2>err &&
962 # Instead of requiring the output to contain one combined line
963 # CONFLICT (rename/rename/delete/delete)
964 # or perhaps two lines:
965 # CONFLICT (rename/rename): ...
966 # CONFLICT (rename/delete): info about pair 1
967 # CONFLICT (rename/delete): info about pair 2
968 # and instead of requiring "rename/rename" instead of "add/add",
969 # be flexible in the type of console output message(s) reported
970 # for this particular case; we will be more stringent about the
971 # contents of the index and working directory.
972 test_i18ngrep "CONFLICT (\(.*\)/\1)" out &&
973 test_i18ngrep "CONFLICT (rename.*delete)" out &&
974 test_must_be_empty err &&
976 git ls-files -s >file_count &&
977 test_line_count = 2 file_count &&
978 git ls-files -u >file_count &&
979 test_line_count = 2 file_count &&
980 git ls-files -o >file_count &&
981 test_line_count = 3 file_count &&
983 git rev-parse >actual \
985 git rev-parse >expect \
988 test_path_is_missing foo &&
989 test_path_is_missing bar &&
990 # baz should have two-way merged contents of the original
991 # contents of foo and bar; check that content from both sides
998 # Testcase mod6, chains of rename/rename(1to2) and rename/rename(2to1)
999 # Commit O: one, three, five
1000 # Commit A: one->two, three->four, five->six
1001 # Commit B: one->six, three->two, five->four
1002 # Expected: six CONFLICT(rename/rename) messages, each path in two of the
1003 # multi-way merged contents found in two, four, six
1005 test_setup_mod6
() {
1006 test_create_repo mod6
&&
1009 test_seq
11 19 >one
&&
1010 test_seq
31 39 >three
&&
1011 test_seq
51 59 >five
&&
1014 git commit
-m "O" &&
1021 test_seq
10 19 >one
&&
1023 git add one three
&&
1025 git
mv three four
&&
1028 git commit
-m "A" &&
1032 echo forty
>>three
&&
1034 git add one three five
&&
1043 test_expect_failure
'mod6-check: chains of rename/rename(1to2) and rename/rename(2to1)' '
1050 test_must_fail git merge -s recursive B^0 >out 2>err &&
1052 test_i18ngrep "CONFLICT (rename/rename)" out &&
1053 test_must_be_empty err &&
1055 git ls-files -s >file_count &&
1056 test_line_count = 9 file_count &&
1057 git ls-files -u >file_count &&
1058 test_line_count = 9 file_count &&
1059 git ls-files -o >file_count &&
1060 test_line_count = 3 file_count &&
1062 test_seq 10 20 >merged-one &&
1063 test_seq 51 60 >merged-five &&
1064 # Determine what the merge of three would give us.
1065 test_seq 31 39 >three-base &&
1066 test_seq 31 40 >three-side-A &&
1067 test_seq 31 39 >three-side-B &&
1068 echo forty >>three-side-B &&
1069 test_must_fail git merge-file \
1073 three-side-A three-base three-side-B &&
1074 sed -e "s/^\([<=>]\)/\1\1/" three-side-A >merged-three &&
1076 # Verify the index is as expected
1077 git rev-parse >actual \
1081 git hash-object >expect \
1082 merged-one merged-three \
1083 merged-three merged-five \
1084 merged-five merged-one &&
1085 test_cmp expect actual &&
1087 git cat-file -p :2:two >expect &&
1088 git cat-file -p :3:two >other &&
1090 test_must_fail git merge-file \
1091 -L "HEAD" -L "" -L "B^0" \
1092 expect empty other &&
1093 test_cmp expect two &&
1095 git cat-file -p :2:four >expect &&
1096 git cat-file -p :3:four >other &&
1097 test_must_fail git merge-file \
1098 -L "HEAD" -L "" -L "B^0" \
1099 expect empty other &&
1100 test_cmp expect four &&
1102 git cat-file -p :2:six >expect &&
1103 git cat-file -p :3:six >other &&
1104 test_must_fail git merge-file \
1105 -L "HEAD" -L "" -L "B^0" \
1106 expect empty other &&
1111 test_conflicts_with_adds_and_renames
() {
1123 # Both L and R have files named 'three' which collide. Each of
1124 # the colliding files could have been involved in a rename, in
1125 # which case there was a file named 'one' or 'two' that was
1126 # modified on the opposite side of history and renamed into the
1127 # collision on this side of history.
1130 # 1) The index should contain both a stage 2 and stage 3 entry
1131 # for the colliding file. Does it?
1132 # 2) When renames are involved, the content merges are clean, so
1133 # the index should reflect the content merges, not merely the
1134 # version of the colliding file from the prior commit. Does
1136 # 3) There should be a file in the worktree named 'three'
1137 # containing the two-way merged contents of the content-merged
1138 # versions of 'three' from each of the two colliding
1139 # files. Is it present?
1140 # 4) There should not be any three~* files in the working
1142 test_setup_collision_conflict
() {
1143 #test_expect_success "setup simple $sideL/$sideR conflict" '
1144 test_create_repo simple_
${sideL}_
${sideR} &&
1146 cd simple_
${sideL}_
${sideR} &&
1148 # Create some related files now
1149 for i
in $
(test_seq
1 10)
1151 echo Random base content line
$i
1153 cp file_v1 file_v2
&&
1154 echo modification
>>file_v2
&&
1156 cp file_v1 file_v3
&&
1157 echo more stuff
>>file_v3
&&
1158 cp file_v3 file_v4
&&
1159 echo yet
more stuff
>>file_v4
&&
1161 # Use a tag to record both these files for simple
1162 # access, and clean out these untracked files
1163 git tag file_v1 $
(git hash-object
-w file_v1
) &&
1164 git tag file_v2 $
(git hash-object
-w file_v2
) &&
1165 git tag file_v3 $
(git hash-object
-w file_v3
) &&
1166 git tag file_v4 $
(git hash-object
-w file_v4
) &&
1169 # Setup original commit (or merge-base), consisting of
1170 # files named "one" and "two" if renames were involved.
1171 touch irrelevant_file
&&
1172 git add irrelevant_file
&&
1173 if [ $sideL = "rename" ]
1175 git show file_v1
>one
&&
1178 if [ $sideR = "rename" ]
1180 git show file_v3
>two
&&
1183 test_tick
&& git commit
-m initial
&&
1188 # Handle the left side
1190 if [ $sideL = "rename" ]
1194 git show file_v2
>three
&&
1197 if [ $sideR = "rename" ]
1199 git show file_v4
>two
&&
1202 test_tick
&& git commit
-m L
&&
1204 # Handle the right side
1206 if [ $sideL = "rename" ]
1208 git show file_v2
>one
&&
1211 if [ $sideR = "rename" ]
1215 git show file_v4
>three
&&
1218 test_tick
&& git commit
-m R
1223 test_expect_success
"check simple $sideL/$sideR conflict" '
1224 test_setup_collision_conflict &&
1226 cd simple_${sideL}_${sideR} &&
1230 # Merge must fail; there is a conflict
1231 test_must_fail git merge -s recursive R^0 &&
1233 # Make sure the index has the right number of entries
1234 git ls-files -s >out &&
1235 test_line_count = 3 out &&
1236 git ls-files -u >out &&
1237 test_line_count = 2 out &&
1238 # Ensure we have the correct number of untracked files
1239 git ls-files -o >out &&
1240 test_line_count = 1 out &&
1242 # Nothing should have touched irrelevant_file
1243 git rev-parse >actual \
1244 :0:irrelevant_file \
1247 git rev-parse >expected \
1248 master:irrelevant_file \
1251 test_cmp expected actual &&
1253 # Make sure we have the correct merged contents for
1255 git show file_v1 >expected &&
1256 cat <<-\EOF >>expected &&
1265 test_cmp expected three
1270 test_conflicts_with_adds_and_renames rename rename
1271 test_conflicts_with_adds_and_renames rename add
1272 test_conflicts_with_adds_and_renames add rename
1273 test_conflicts_with_adds_and_renames add add
1283 # master has two files, named 'one' and 'two'.
1284 # branches L and R both modify 'one', in conflicting ways.
1285 # branches L and R both modify 'two', in conflicting ways.
1286 # branch L also renames 'one' to 'three'.
1287 # branch R also renames 'two' to 'three'.
1289 # So, we have four different conflicting files that all end up at path
1291 test_setup_nested_conflicts_from_rename_rename
() {
1292 test_create_repo nested_conflicts_from_rename_rename
&&
1294 cd nested_conflicts_from_rename_rename
&&
1296 # Create some related files now
1297 for i
in $
(test_seq
1 10)
1299 echo Random base content line
$i
1302 cp file_v1 file_v2
&&
1303 cp file_v1 file_v3
&&
1304 cp file_v1 file_v4
&&
1305 cp file_v1 file_v5
&&
1306 cp file_v1 file_v6
&&
1308 echo one
>>file_v1
&&
1309 echo uno
>>file_v2
&&
1310 echo eins
>>file_v3
&&
1312 echo two
>>file_v4
&&
1313 echo dos
>>file_v5
&&
1314 echo zwei
>>file_v6
&&
1316 # Setup original commit (or merge-base), consisting of
1317 # files named "one" and "two".
1321 test_tick
&& git commit
-m english
&&
1326 # Handle the left side
1329 mv -f file_v2 three
&&
1330 mv -f file_v5 two
&&
1331 git add two three
&&
1332 test_tick
&& git commit
-m spanish
&&
1334 # Handle the right side
1337 mv -f file_v3 one
&&
1338 mv -f file_v6 three
&&
1339 git add one three
&&
1340 test_tick
&& git commit
-m german
1344 test_expect_success
'check nested conflicts from rename/rename(2to1)' '
1345 test_setup_nested_conflicts_from_rename_rename &&
1347 cd nested_conflicts_from_rename_rename &&
1351 # Merge must fail; there is a conflict
1352 test_must_fail git merge -s recursive R^0 &&
1354 # Make sure the index has the right number of entries
1355 git ls-files -s >out &&
1356 test_line_count = 2 out &&
1357 git ls-files -u >out &&
1358 test_line_count = 2 out &&
1359 # Ensure we have the correct number of untracked files
1360 git ls-files -o >out &&
1361 test_line_count = 1 out &&
1363 # Compare :2:three to expected values
1364 git cat-file -p master:one >base &&
1365 git cat-file -p L:three >ours &&
1366 git cat-file -p R:one >theirs &&
1367 test_must_fail git merge-file \
1368 -L "HEAD:three" -L "" -L "R^0:one" \
1370 sed -e "s/^\([<=>]\)/\1\1/" ours >L-three &&
1371 git cat-file -p :2:three >expect &&
1372 test_cmp expect L-three &&
1374 # Compare :2:three to expected values
1375 git cat-file -p master:two >base &&
1376 git cat-file -p L:two >ours &&
1377 git cat-file -p R:three >theirs &&
1378 test_must_fail git merge-file \
1379 -L "HEAD:two" -L "" -L "R^0:three" \
1381 sed -e "s/^\([<=>]\)/\1\1/" ours >R-three &&
1382 git cat-file -p :3:three >expect &&
1383 test_cmp expect R-three &&
1385 # Compare three to expected contents
1387 test_must_fail git merge-file \
1388 -L "HEAD" -L "" -L "R^0" \
1389 L-three empty R-three &&
1390 test_cmp three L-three
1394 # Testcase rename/rename(1to2) of a binary file
1398 # Expected: CONFLICT(rename/rename) message, three unstaged entries in the
1399 # index, and contents of orig-[AB] at path orig-[AB]
1400 test_setup_rename_rename_1_to_2_binary
() {
1401 test_create_repo rename_rename_1_to_2_binary
&&
1403 cd rename_rename_1_to_2_binary
&&
1405 echo '* binary' >.gitattributes
&&
1406 git add .gitattributes
&&
1408 test_seq
1 10 >orig
&&
1410 git commit
-m orig
&&
1416 git
mv orig orig-A
&&
1417 test_seq
1 11 >orig-A
&&
1419 git commit
-m orig-A
&&
1422 git
mv orig orig-B
&&
1423 test_seq
0 10 >orig-B
&&
1425 git commit
-m orig-B
1430 test_expect_success
'rename/rename(1to2) with a binary file' '
1431 test_setup_rename_rename_1_to_2_binary &&
1433 cd rename_rename_1_to_2_binary &&
1437 test_must_fail git merge -s recursive B^0 &&
1439 # Make sure the index has the right number of entries
1440 git ls-files -s >actual &&
1441 test_line_count = 4 actual &&
1443 git rev-parse A:orig-A B:orig-B >expect &&
1444 git hash-object orig-A orig-B >actual &&
1445 test_cmp expect actual