git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCHv4 4/6] merge_recursive: Fix renames across paths below D/F conflicts

From
Elijah Newren <newren@gmail.com>
Date
Jul 9, 2010, 13:10 UTC
Message-ID
<1278681056-31460-5-git-send-email-newren@gmail.com>
In-Reply-To
<1278681056-31460-1-git-send-email-newren@gmail.com>

The rename logic in process_renames() handles renames and merging of file contents and then marks files as processed. However, there may be higher stage entries left in the index for other reasons (e.g., due to D/F conflicts). By checking for such cases and marking the entry as not processed, it allows process_entry() later to look at it and handle those higher stages.

Signed-off-by: Elijah Newren <newren@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
---
 merge-recursive.c               |   15 +++++++++++++--
 t/t3509-cherry-pick-merge-df.sh |    2 +-
 t/t6020-merge-df.sh             |    2 +-
 3 files changed, 15 insertions(+), 4 deletions(-)
diff --git a/merge-recursive.c b/merge-recursive.c
index 7d0c27d..8f4b7d4 100644
--- a/merge-recursive.c
+++ b/merge-recursive.c
@@ -1019,14 +1019,25 @@ static int process_renames(struct merge_options *o,
 
 				if (mfi.clean &&
 				    sha_eq(mfi.sha, ren1->pair->two->sha1) &&
-				    mfi.mode == ren1->pair->two->mode)
+				    mfi.mode == ren1->pair->two->mode) {
 					/*
 					 * This messaged is part of
 					 * t6022 test. If you change
 					 * it update the test too.
 					 */
 					output(o, 3, "Skipped %s (merged same as existing)", ren1_dst);
-				else {
+
+					/* There may be higher stage entries left
+					 * in the index (e.g. due to a D/F
+					 * conflict) that need to be resolved.
+					 */
+					for (i = 1; i <= 3; i++) {
+						if (!ren1->dst_entry->stages[i].mode)
+							continue;
+						ren1->dst_entry->processed = 0;
+						break;
+					}
+				} else {
 					if (mfi.merge || !mfi.clean)
 						output(o, 1, "Renaming %s => %s", ren1_src, ren1_dst);
 					if (mfi.merge)
diff --git a/t/t3509-cherry-pick-merge-df.sh b/t/t3509-cherry-pick-merge-df.sh
index 7c05e16..6e7ef84 100755
--- a/t/t3509-cherry-pick-merge-df.sh
+++ b/t/t3509-cherry-pick-merge-df.sh
@@ -26,7 +26,7 @@ test_expect_success 'Setup rename across paths each below D/F conflicts' '
 	git commit -m f1
 '
 
-test_expect_failure 'Cherry-pick succeeds with rename across D/F conflicts' '
+test_expect_success 'Cherry-pick succeeds with rename across D/F conflicts' '
 	git reset --hard &&
 	git checkout master^0 &&
 	git cherry-pick branch
diff --git a/t/t6020-merge-df.sh b/t/t6020-merge-df.sh
index e71c687..490d397 100755
--- a/t/t6020-merge-df.sh
+++ b/t/t6020-merge-df.sh
@@ -22,7 +22,7 @@ git commit -m "File: dir"'
 
 test_expect_code 1 'Merge with d/f conflicts' 'git merge "merge msg" B master'
 
-test_expect_failure 'F/D conflict' '
+test_expect_success 'F/D conflict' '
 	git reset --hard &&
 	git checkout master &&
 	rm .git/index &&
-- 
1.7.1.1.23.gafea6
Previous: Elijah NewrenNext: Elijah Newren
Message 5 of 7 in “[PATCHv4 0/6] D/F conflict fixes”
  1. Elijah NewrenJul 9, 2010
  2. 1/6 Add additional testcases for D/F conflictsElijah Newren, Jul 9, 2010
  3. 2/6 Add a rename + D/F conflict testcaseElijah Newren, Jul 9, 2010
  4. 3/6 merge-recursive: Fix D/F conflictsElijah Newren, Jul 9, 2010
  5. 4/6 merge_recursive: Fix renames across paths below D/F conflictsElijah Newren, Jul 9, 2010
  6. 5/6 fast-export: Fix output order of D/F changesElijah Newren, Jul 9, 2010
  7. 6/6 fast-import: Improve robustness when D->F changes provided in wrong orderElijah Newren, Jul 9, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.