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_expect_success 'setup rename/delete + untracked file' '
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?" '
36 cd rename-delete-untracked &&
38 test_must_fail git merge -s recursive rename-the-ring &&
40 # Make sure git did not delete an untracked file
41 test_path_is_file ring
45 # Testcase setup for rename/modify/add-source:
46 # Commit A: new file: a
47 # Commit B: modify a slightly
48 # Commit C: rename a->b, add completely different a
50 # We should be able to merge B & C cleanly
52 test_expect_success 'setup rename/modify/add-source conflict' '
53 test_create_repo rename-modify-add-source &&
55 cd rename-modify-add-source &&
57 printf "1\n2\n3\n4\n5\n6\n7\n" >a &&
62 git checkout -b B A &&
67 git checkout -b C A &&
69 echo something completely different >a &&
75 test_expect_failure 'rename/modify/add-source conflict resolvable' '
77 cd rename-modify-add-source &&
81 git merge -s recursive C^0 &&
83 git rev-parse >expect \
85 git rev-parse >actual \
87 test_cmp expect actual
91 test_expect_success 'setup resolvable conflict missed if rename missed' '
92 test_create_repo break-detection-1 &&
94 cd break-detection-1 &&
96 printf "1\n2\n3\n4\n5\n" >a &&
102 git checkout -b B A &&
104 echo "Completely different content" >a &&
108 git checkout -b C A &&
115 test_expect_failure 'conflict caused if rename not detected' '
117 cd break-detection-1 &&
119 git checkout -q C^0 &&
120 git merge -s recursive B^0 &&
122 git ls-files -s >out &&
123 test_line_count = 3 out &&
124 git ls-files -u >out &&
125 test_line_count = 0 out &&
126 git ls-files -o >out &&
127 test_line_count = 1 out &&
129 test_line_count = 6 c &&
130 git rev-parse >expect \
132 git rev-parse >actual \
134 test_cmp expect actual
138 test_expect_success 'setup conflict resolved wrong if rename missed' '
139 test_create_repo break-detection-2 &&
141 cd break-detection-2 &&
143 printf "1\n2\n3\n4\n5\n" >a &&
149 git checkout -b D A &&
153 echo "Completely different content" >a &&
157 git checkout -b E A &&
159 echo "Completely different content" >>a &&
165 test_expect_failure 'missed conflict if rename not detected' '
167 cd break-detection-2 &&
169 git checkout -q E^0 &&
170 test_must_fail git merge -s recursive D^0
174 # Tests for undetected rename/add-source causing a file to erroneously be
175 # deleted (and for mishandled rename/rename(1to1) causing the same issue).
177 # This test uses a rename/rename(1to1)+add-source conflict (1to1 means the
178 # same file is renamed on both sides to the same thing; it should trigger
179 # the 1to2 logic, which it would do if the add-source didn't cause issues
180 # for git's rename detection):
181 # Commit A: new file: a
182 # Commit B: rename a->b
183 # Commit C: rename a->b, add unrelated a
185 test_expect_success 'setup undetected rename/add-source causes data loss' '
186 test_create_repo break-detection-3 &&
188 cd break-detection-3 &&
190 printf "1\n2\n3\n4\n5\n" >a &&
195 git checkout -b B A &&
199 git checkout -b C A &&
207 test_expect_failure 'detect rename/add-source and preserve all data' '
209 cd break-detection-3 &&
213 git merge -s recursive C^0 &&
215 git ls-files -s >out &&
216 test_line_count = 2 out &&
217 git ls-files -u >out &&
218 test_line_count = 2 out &&
219 git ls-files -o >out &&
220 test_line_count = 1 out &&
222 test_path_is_file a &&
223 test_path_is_file b &&
225 git rev-parse >expect \
227 git rev-parse >actual \
229 test_cmp expect actual
233 test_expect_failure 'detect rename/add-source and preserve all data, merge other way' '
235 cd break-detection-3 &&
239 git merge -s recursive B^0 &&
241 git ls-files -s >out &&
242 test_line_count = 2 out &&
243 git ls-files -u >out &&
244 test_line_count = 2 out &&
245 git ls-files -o >out &&
246 test_line_count = 1 out &&
248 test_path_is_file a &&
249 test_path_is_file b &&
251 git rev-parse >expect \
253 git rev-parse >actual \
255 test_cmp expect actual
259 test_expect_success 'setup content merge + rename/directory conflict' '
260 test_create_repo rename-directory-1 &&
262 cd rename-directory-1 &&
264 printf "1\n2\n3\n4\n5\n6\n" >file &&
267 git commit -m base &&
270 git checkout -b right &&
273 echo junk >newfile/realfile &&
274 git add file newfile/realfile &&
276 git commit -m right &&
278 git checkout -b left-conflict base &&
281 git mv file newfile &&
283 git commit -m left &&
285 git checkout -b left-clean base &&
287 cat file >>newfile &&
295 test_expect_success 'rename/directory conflict + clean content merge' '
297 cd rename-directory-1 &&
299 git checkout left-clean^0 &&
301 test_must_fail git merge -s recursive right^0 &&
303 git ls-files -s >out &&
304 test_line_count = 2 out &&
305 git ls-files -u >out &&
306 test_line_count = 1 out &&
307 git ls-files -o >out &&
308 test_line_count = 2 out &&
311 git cat-file -p base:file >>expect &&
313 test_cmp expect newfile~HEAD &&
315 test $(git rev-parse :2:newfile) = $(git hash-object expect) &&
317 test_path_is_file newfile/realfile &&
318 test_path_is_file newfile~HEAD
322 test_expect_success 'rename/directory conflict + content merge conflict' '
324 cd rename-directory-1 &&
329 git checkout left-conflict^0 &&
331 test_must_fail git merge -s recursive right^0 &&
333 git ls-files -s >out &&
334 test_line_count = 4 out &&
335 git ls-files -u >out &&
336 test_line_count = 3 out &&
337 git ls-files -o >out &&
338 test_line_count = 2 out &&
340 git cat-file -p left-conflict:newfile >left &&
341 git cat-file -p base:file >base &&
342 git cat-file -p right:file >right &&
343 test_must_fail git merge-file \
348 test_cmp left newfile~HEAD &&
350 git rev-parse >expect \
351 base:file left-conflict:newfile right:file &&
352 git rev-parse >actual \
353 :1:newfile :2:newfile :3:newfile &&
354 test_cmp expect actual &&
356 test_path_is_file newfile/realfile &&
357 test_path_is_file newfile~HEAD
361 test_expect_success 'setup content merge + rename/directory conflict w/ disappearing dir' '
362 test_create_repo rename-directory-2 &&
364 cd rename-directory-2 &&
367 printf "1\n2\n3\n4\n5\n6\n" >sub/file &&
370 git commit -m base &&
373 git checkout -b right &&
377 git commit -m right &&
379 git checkout -b left base &&
381 cat sub/file >>newfile &&
390 test_expect_success 'disappearing dir in rename/directory conflict handled' '
392 cd rename-directory-2 &&
394 git checkout left^0 &&
396 git merge -s recursive right^0 &&
398 git ls-files -s >out &&
399 test_line_count = 1 out &&
400 git ls-files -u >out &&
401 test_line_count = 0 out &&
402 git ls-files -o >out &&
403 test_line_count = 1 out &&
406 git cat-file -p base:sub/file >>expect &&
408 test_cmp expect sub &&
410 test_path_is_file sub
414 # Test for all kinds of things that can go wrong with rename/rename (2to1):
415 # Commit A: new files: a & b
416 # Commit B: rename a->c, modify b
417 # Commit C: rename b->c, modify a
419 # Merging of B & C should NOT be clean. Questions:
420 # * Both a & b should be removed by the merge; are they?
421 # * The two c's should contain modifications to a & b; do they?
422 # * The index should contain two files, both for c; does it?
423 # * The working copy should have two files, both of form c~<unique>; does it?
424 # * Nothing else should be present. Is anything?
426 test_expect_success 'setup rename/rename (2to1) + modify/modify' '
427 test_create_repo rename-rename-2to1 &&
429 cd rename-rename-2to1 &&
431 printf "1\n2\n3\n4\n5\n" >a &&
432 printf "5\n4\n3\n2\n1\n" >b &&
437 git checkout -b B A &&
443 git checkout -b C A &&
451 test_expect_success 'handle rename/rename (2to1) conflict correctly' '
453 cd rename-rename-2to1 &&
457 test_must_fail git merge -s recursive C^0 >out &&
458 test_i18ngrep "CONFLICT (rename/rename)" out &&
460 git ls-files -s >out &&
461 test_line_count = 2 out &&
462 git ls-files -u >out &&
463 test_line_count = 2 out &&
464 git ls-files -u c >out &&
465 test_line_count = 2 out &&
466 git ls-files -o >out &&
467 test_line_count = 1 out &&
469 test_path_is_missing a &&
470 test_path_is_missing b &&
472 git rev-parse >expect \
474 git rev-parse >actual \
476 test_cmp expect actual &&
478 # Test that the two-way merge in new_a is as expected
479 git cat-file -p :2:c >>ours &&
480 git cat-file -p :3:c >>theirs &&
482 test_must_fail git merge-file \
487 git hash-object c >actual &&
488 git hash-object ours >expect &&
489 test_cmp expect actual
493 # Testcase setup for simple rename/rename (1to2) conflict:
494 # Commit A: new file: a
495 # Commit B: rename a->b
496 # Commit C: rename a->c
497 test_expect_success 'setup simple rename/rename (1to2) conflict' '
498 test_create_repo rename-rename-1to2 &&
500 cd rename-rename-1to2 &&
508 git checkout -b B A &&
513 git checkout -b C A &&
520 test_expect_success 'merge has correct working tree contents' '
522 cd rename-rename-1to2 &&
526 test_must_fail git merge -s recursive B^0 &&
528 git ls-files -s >out &&
529 test_line_count = 3 out &&
530 git ls-files -u >out &&
531 test_line_count = 3 out &&
532 git ls-files -o >out &&
533 test_line_count = 1 out &&
535 test_path_is_missing a &&
536 git rev-parse >expect \
539 git rev-parse >actual \
541 git hash-object >>actual \
543 test_cmp expect actual
547 # Testcase setup for rename/rename(1to2)/add-source conflict:
548 # Commit A: new file: a
549 # Commit B: rename a->b
550 # Commit C: rename a->c, add completely different a
552 # Merging of B & C should NOT be clean; there's a rename/rename conflict
554 test_expect_success 'setup rename/rename(1to2)/add-source conflict' '
555 test_create_repo rename-rename-1to2-add-source-1 &&
557 cd rename-rename-1to2-add-source-1 &&
559 printf "1\n2\n3\n4\n5\n6\n7\n" >a &&
564 git checkout -b B A &&
568 git checkout -b C A &&
570 echo something completely different >a &&
576 test_expect_failure 'detect conflict with rename/rename(1to2)/add-source merge' '
578 cd rename-rename-1to2-add-source-1 &&
582 test_must_fail git merge -s recursive C^0 &&
584 git ls-files -s >out &&
585 test_line_count = 4 out &&
586 git ls-files -o >out &&
587 test_line_count = 1 out &&
589 git rev-parse >expect \
591 git rev-parse >actual \
592 :3:a :1:a :2:b :3:c &&
593 test_cmp expect actual &&
595 test_path_is_file a &&
596 test_path_is_file b &&
601 test_expect_success 'setup rename/rename(1to2)/add-source resolvable conflict' '
602 test_create_repo rename-rename-1to2-add-source-2 &&
604 cd rename-rename-1to2-add-source-2 &&
609 git commit -m base &&
612 git checkout -b B A &&
617 git checkout -b C A &&
619 echo important-info >a &&
626 test_expect_failure 'rename/rename/add-source still tracks new a file' '
628 cd rename-rename-1to2-add-source-2 &&
631 git merge -s recursive B^0 &&
633 git ls-files -s >out &&
634 test_line_count = 2 out &&
635 git ls-files -o >out &&
636 test_line_count = 1 out &&
638 git rev-parse >expect \
640 git rev-parse >actual \
642 test_cmp expect actual
646 test_expect_success 'setup rename/rename(1to2)/add-dest conflict' '
647 test_create_repo rename-rename-1to2-add-dest &&
649 cd rename-rename-1to2-add-dest &&
654 git commit -m base &&
657 git checkout -b B A &&
659 echo precious-data >c &&
664 git checkout -b C A &&
666 echo important-info >b &&
673 test_expect_success 'rename/rename/add-dest merge still knows about conflicting file versions' '
675 cd rename-rename-1to2-add-dest &&
678 test_must_fail git merge -s recursive B^0 &&
680 git ls-files -s >out &&
681 test_line_count = 5 out &&
682 git ls-files -u b >out &&
683 test_line_count = 2 out &&
684 git ls-files -u c >out &&
685 test_line_count = 2 out &&
686 git ls-files -o >out &&
687 test_line_count = 1 out &&
689 git rev-parse >expect \
690 A:a C:b B:b C:c B:c &&
691 git rev-parse >actual \
692 :1:a :2:b :3:b :2:c :3:c &&
693 test_cmp expect actual &&
695 # Record some contents for re-doing merges
696 git cat-file -p A:a >stuff &&
697 git cat-file -p C:b >important_info &&
698 git cat-file -p B:c >precious_data &&
701 # Test the merge in b
702 test_must_fail git merge-file \
706 important_info empty stuff &&
707 test_cmp important_info b &&
709 # Test the merge in c
710 test_must_fail git merge-file \
714 stuff empty precious_data &&
719 # Testcase rad, rename/add/delete
721 # Commit A: rm foo, add different bar
722 # Commit B: rename foo->bar
723 # Expected: CONFLICT (rename/add/delete), two-way merged bar
725 test_expect_success 'rad-setup: rename/add/delete conflict' '
726 test_create_repo rad &&
729 echo "original file" >foo &&
731 git commit -m "original" &&
739 echo "different file" >bar &&
741 git commit -m "Remove foo, add bar" &&
745 git commit -m "rename foo to bar"
749 test_expect_failure 'rad-check: rename/add/delete conflict' '
754 test_must_fail git merge -s recursive A^0 >out 2>err &&
756 # Not sure whether the output should contain just one
757 # "CONFLICT (rename/add/delete)" line, or if it should break
758 # it into a pair of "CONFLICT (rename/delete)" and
759 # "CONFLICT (rename/add)"; allow for either.
760 test_i18ngrep "CONFLICT (rename.*add)" out &&
761 test_i18ngrep "CONFLICT (rename.*delete)" out &&
762 test_must_be_empty err &&
764 git ls-files -s >file_count &&
765 test_line_count = 2 file_count &&
766 git ls-files -u >file_count &&
767 test_line_count = 2 file_count &&
768 git ls-files -o >file_count &&
769 test_line_count = 2 file_count &&
771 git rev-parse >actual \
773 git rev-parse >expect \
776 test_cmp file_is_missing foo &&
777 # bar should have two-way merged contents of the different
778 # versions of bar; check that content from both sides is
785 # Testcase rrdd, rename/rename(2to1)/delete/delete
787 # Commit A: rename foo->baz, rm bar
788 # Commit B: rename bar->baz, rm foo
789 # Expected: CONFLICT (rename/rename/delete/delete), two-way merged baz
791 test_expect_success 'rrdd-setup: rename/rename(2to1)/delete/delete conflict' '
792 test_create_repo rrdd &&
807 git commit -m "Rename foo, remove bar" &&
812 git commit -m "Rename bar, remove foo"
816 test_expect_failure 'rrdd-check: rename/rename(2to1)/delete/delete conflict' '
821 test_must_fail git merge -s recursive B^0 >out 2>err &&
823 # Not sure whether the output should contain just one
824 # "CONFLICT (rename/rename/delete/delete)" line, or if it
825 # should break it into three: "CONFLICT (rename/rename)" and
826 # two "CONFLICT (rename/delete)" lines; allow for either.
827 test_i18ngrep "CONFLICT (rename/rename)" out &&
828 test_i18ngrep "CONFLICT (rename.*delete)" out &&
829 test_must_be_empty err &&
831 git ls-files -s >file_count &&
832 test_line_count = 2 file_count &&
833 git ls-files -u >file_count &&
834 test_line_count = 2 file_count &&
835 git ls-files -o >file_count &&
836 test_line_count = 2 file_count &&
838 git rev-parse >actual \
840 git rev-parse >expect \
843 test_cmp file_is_missing foo &&
844 test_cmp file_is_missing bar &&
845 # baz should have two-way merged contents of the original
846 # contents of foo and bar; check that content from both sides
853 # Testcase mod6, chains of rename/rename(1to2) and rename/rename(2to1)
854 # Commit O: one, three, five
855 # Commit A: one->two, three->four, five->six
856 # Commit B: one->six, three->two, five->four
857 # Expected: six CONFLICT(rename/rename) messages, each path in two of the
858 # multi-way merged contents found in two, four, six
860 test_expect_success 'mod6-setup: chains of rename/rename(1to2) and rename/rename(2to1)' '
861 test_create_repo mod6 &&
864 test_seq 11 19 >one &&
865 test_seq 31 39 >three &&
866 test_seq 51 59 >five &&
876 test_seq 10 19 >one &&
887 echo forty >>three &&
889 git add one three five &&
898 test_expect_failure 'mod6-check: chains of rename/rename(1to2) and rename/rename(2to1)' '
904 test_must_fail git merge -s recursive B^0 >out 2>err &&
906 test_i18ngrep "CONFLICT (rename/rename)" out &&
907 test_must_be_empty err &&
909 git ls-files -s >file_count &&
910 test_line_count = 6 file_count &&
911 git ls-files -u >file_count &&
912 test_line_count = 6 file_count &&
913 git ls-files -o >file_count &&
914 test_line_count = 3 file_count &&
916 test_seq 10 20 >merged-one &&
917 test_seq 51 60 >merged-five &&
918 # Determine what the merge of three would give us.
919 test_seq 30 40 >three-side-A &&
920 test_seq 31 39 >three-side-B &&
921 echo forty >three-side-B &&
923 test_must_fail git merge-file \
927 three-side-A empty three-side-B &&
928 sed -e "s/^\([<=>]\)/\1\1\1/" three-side-A >merged-three &&
930 # Verify the index is as expected
931 git rev-parse >actual \
935 git hash-object >expect \
936 merged-one merged-three \
937 merged-three merged-five \
938 merged-five merged-one &&
939 test_cmp expect actual &&
941 git cat-file -p :2:two >expect &&
942 git cat-file -p :3:two >other &&
943 test_must_fail git merge-file \
944 -L "HEAD" -L "" -L "B^0" \
945 expect empty other &&
946 test_cmp expect two &&
948 git cat-file -p :2:four >expect &&
949 git cat-file -p :3:four >other &&
950 test_must_fail git merge-file \
951 -L "HEAD" -L "" -L "B^0" \
952 expect empty other &&
953 test_cmp expect four &&
955 git cat-file -p :2:six >expect &&
956 git cat-file -p :3:six >other &&
957 test_must_fail git merge-file \
958 -L "HEAD" -L "" -L "B^0" \
959 expect empty other &&
964 test_conflicts_with_adds_and_renames() {
976 # Both L and R have files named 'three' which collide. Each of
977 # the colliding files could have been involved in a rename, in
978 # which case there was a file named 'one' or 'two' that was
979 # modified on the opposite side of history and renamed into the
980 # collision on this side of history.
983 # 1) The index should contain both a stage 2 and stage 3 entry
984 # for the colliding file. Does it?
985 # 2) When renames are involved, the content merges are clean, so
986 # the index should reflect the content merges, not merely the
987 # version of the colliding file from the prior commit. Does
989 # 3) There should be a file in the worktree named 'three'
990 # containing the two-way merged contents of the content-merged
991 # versions of 'three' from each of the two colliding
992 # files. Is it present?
993 # 4) There should not be any three~* files in the working
995 test_expect_success "setup simple $sideL/$sideR conflict" '
996 test_create_repo simple_${sideL}_${sideR} &&
998 cd simple_${sideL}_${sideR} &&
1000 # Create some related files now
1001 for i in $(test_seq 1 10)
1003 echo Random base content line $i
1005 cp file_v1 file_v2 &&
1006 echo modification >>file_v2 &&
1008 cp file_v1 file_v3 &&
1009 echo more stuff >>file_v3 &&
1010 cp file_v3 file_v4 &&
1011 echo yet more stuff >>file_v4 &&
1013 # Use a tag to record both these files for simple
1014 # access, and clean out these untracked files
1015 git tag file_v1 $(git hash-object -w file_v1) &&
1016 git tag file_v2 $(git hash-object -w file_v2) &&
1017 git tag file_v3 $(git hash-object -w file_v3) &&
1018 git tag file_v4 $(git hash-object -w file_v4) &&
1021 # Setup original commit (or merge-base), consisting of
1022 # files named "one" and "two" if renames were involved.
1023 touch irrelevant_file &&
1024 git add irrelevant_file &&
1025 if [ $sideL = "rename" ]
1027 git show file_v1 >one &&
1030 if [ $sideR = "rename" ]
1032 git show file_v3 >two &&
1035 test_tick && git commit -m initial &&
1040 # Handle the left side
1042 if [ $sideL = "rename" ]
1046 git show file_v2 >three &&
1049 if [ $sideR = "rename" ]
1051 git show file_v4 >two &&
1054 test_tick && git commit -m L &&
1056 # Handle the right side
1058 if [ $sideL = "rename" ]
1060 git show file_v2 >one &&
1063 if [ $sideR = "rename" ]
1067 git show file_v4 >three &&
1070 test_tick && git commit -m R
1074 test_expect_success "check simple $sideL/$sideR conflict" '
1076 cd simple_${sideL}_${sideR} &&
1080 # Merge must fail; there is a conflict
1081 test_must_fail git merge -s recursive R^0 &&
1083 # Make sure the index has the right number of entries
1084 git ls-files -s >out &&
1085 test_line_count = 3 out &&
1086 git ls-files -u >out &&
1087 test_line_count = 2 out &&
1088 # Ensure we have the correct number of untracked files
1089 git ls-files -o >out &&
1090 test_line_count = 1 out &&
1092 # Nothing should have touched irrelevant_file
1093 git rev-parse >actual \
1094 :0:irrelevant_file \
1097 git rev-parse >expected \
1098 master:irrelevant_file \
1101 test_cmp expected actual &&
1103 # Make sure we have the correct merged contents for
1105 git show file_v1 >expected &&
1106 cat <<-\EOF >>expected &&
1115 test_cmp expected three
1120 test_conflicts_with_adds_and_renames rename rename
1121 test_conflicts_with_adds_and_renames rename add
1122 test_conflicts_with_adds_and_renames add rename
1123 test_conflicts_with_adds_and_renames add add
1133 # master has two files, named 'one' and 'two'.
1134 # branches L and R both modify 'one', in conflicting ways.
1135 # branches L and R both modify 'two', in conflicting ways.
1136 # branch L also renames 'one' to 'three'.
1137 # branch R also renames 'two' to 'three'.
1139 # So, we have four different conflicting files that all end up at path
1141 test_expect_success 'setup nested conflicts from rename/rename(2to1)' '
1142 test_create_repo nested_conflicts_from_rename_rename &&
1144 cd nested_conflicts_from_rename_rename &&
1146 # Create some related files now
1147 for i in $(test_seq 1 10)
1149 echo Random base content line $i
1152 cp file_v1 file_v2 &&
1153 cp file_v1 file_v3 &&
1154 cp file_v1 file_v4 &&
1155 cp file_v1 file_v5 &&
1156 cp file_v1 file_v6 &&
1158 echo one >>file_v1 &&
1159 echo uno >>file_v2 &&
1160 echo eins >>file_v3 &&
1162 echo two >>file_v4 &&
1163 echo dos >>file_v5 &&
1164 echo zwei >>file_v6 &&
1166 # Setup original commit (or merge-base), consisting of
1167 # files named "one" and "two".
1171 test_tick && git commit -m english &&
1176 # Handle the left side
1179 mv -f file_v2 three &&
1180 mv -f file_v5 two &&
1181 git add two three &&
1182 test_tick && git commit -m spanish &&
1184 # Handle the right side
1187 mv -f file_v3 one &&
1188 mv -f file_v6 three &&
1189 git add one three &&
1190 test_tick && git commit -m german
1194 test_expect_success 'check nested conflicts from rename/rename(2to1)' '
1196 cd nested_conflicts_from_rename_rename &&
1200 # Merge must fail; there is a conflict
1201 test_must_fail git merge -s recursive R^0 &&
1203 # Make sure the index has the right number of entries
1204 git ls-files -s >out &&
1205 test_line_count = 2 out &&
1206 git ls-files -u >out &&
1207 test_line_count = 2 out &&
1208 # Ensure we have the correct number of untracked files
1209 git ls-files -o >out &&
1210 test_line_count = 1 out &&
1212 # Compare :2:three to expected values
1213 git cat-file -p master:one >base &&
1214 git cat-file -p L:three >ours &&
1215 git cat-file -p R:one >theirs &&
1216 test_must_fail git merge-file \
1217 -L "HEAD:three" -L "" -L "R^0:one" \
1219 sed -e "s/^\([<=>]\)/\1\1/" ours >L-three &&
1220 git cat-file -p :2:three >expect &&
1221 test_cmp expect L-three &&
1223 # Compare :2:three to expected values
1224 git cat-file -p master:two >base &&
1225 git cat-file -p L:two >ours &&
1226 git cat-file -p R:three >theirs &&
1227 test_must_fail git merge-file \
1228 -L "HEAD:two" -L "" -L "R^0:three" \
1230 sed -e "s/^\([<=>]\)/\1\1/" ours >R-three &&
1231 git cat-file -p :3:three >expect &&
1232 test_cmp expect R-three &&
1234 # Compare three to expected contents
1236 test_must_fail git merge-file \
1237 -L "HEAD" -L "" -L "R^0" \
1238 L-three empty R-three &&
1239 test_cmp three L-three