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

[PATCH v3 3/8] merge-recursive: -Xindex-only to leave worktree unchanged

From
Thomas Rast <tr@thomasrast.ch>
Date
Sep 6, 2014, 17:57 UTC
Message-ID
<5d5715639af05dfd640d1a9827d10480e1313905.1409860234.git.tr@thomasrast.ch>
In-Reply-To
<cover.1409860234.git.tr@thomasrast.ch>
From: Thomas Rast <trast@inf.ethz.ch>

Using the new no_worktree flag from the previous commit, we can teach merge-recursive to leave the worktree untouched. Expose this with a new strategy option so that scripts can use it.

Signed-off-by: Junio C Hamano <gitster@pobox.com>
---
 Documentation/merge-strategies.txt |  4 ++++
 merge-recursive.c                  |  2 ++
 t/t3030-merge-recursive.sh         | 13 +++++++++++++
 3 files changed, 19 insertions(+)
diff --git a/Documentation/merge-strategies.txt b/Documentation/merge-strategies.txt
index 7bbd19b..7716fda 100644
--- a/Documentation/merge-strategies.txt
+++ b/Documentation/merge-strategies.txt
@@ -92,6 +92,10 @@ subtree[=<path>];;
 	is prefixed (or stripped from the beginning) to make the shape of
 	two trees to match.
 
+index-only;;
+	Write the merge result only to the index; do not touch the
+	worktree.
+
 octopus::
 	This resolves cases with more than two heads, but refuses to do
 	a complex merge that needs manual resolution.  It is
diff --git a/merge-recursive.c b/merge-recursive.c
index 059ad03..d54bac2 100644
--- a/merge-recursive.c
+++ b/merge-recursive.c
@@ -2108,6 +2108,8 @@ int parse_merge_opt(struct merge_options *o, const char *s)
 		if ((o->rename_score = parse_rename_score(&arg)) == -1 || *arg != 0)
 			return -1;
 	}
+	else if (!strcmp(s, "index-only"))
+		o->no_worktree = 1;
 	else
 		return -1;
 	return 0;
diff --git a/t/t3030-merge-recursive.sh b/t/t3030-merge-recursive.sh
index 82e1854..be07705 100755
--- a/t/t3030-merge-recursive.sh
+++ b/t/t3030-merge-recursive.sh
@@ -297,6 +297,19 @@ test_expect_success 'merge-recursive result' '
 
 '
 
+test_expect_success 'merge-recursive --index-only' '
+
+	rm -fr [abcd] &&
+	git checkout -f "$c2" &&
+	test_expect_code 1 git merge-recursive --index-only "$c0" -- "$c2" "$c1" &&
+	git ls-files -s >actual &&
+	# reuses "expected" from previous test!
+	test_cmp expected actual &&
+	git diff HEAD >actual-diff &&
+	: >expected-diff &&
+	test_cmp expected-diff actual-diff
+'
+
 test_expect_success 'fail if the index has unresolved entries' '
 
 	rm -fr [abcd] &&
-- 
2.1.0.72.g9b94086
Previous: Junio C HamanoNext: Thomas Rast
Message 5 of 18 in “--remerge-diff”
  1. 0/8 --remerge-diffThomas Rast, Sep 6, 2014
  2. 1/8 merge-recursive: remove dead conditional in update_stages()Thomas Rast, Sep 6, 2014
  3. 2/8 merge-recursive: internal flag to avoid touching the worktreeThomas Rast, Sep 6, 2014
  4. Junio C HamanoSep 8, 2014
  5. 3/8 merge-recursive: -Xindex-only to leave worktree unchangedThomas Rast, Sep 6, 2014
  6. 4/8 combine-diff: do not pass revs->dense_combined_merges redundantlyThomas Rast, Sep 6, 2014
  7. Junio C HamanoSep 8, 2014
  8. Jens LehmannSep 11, 2014
  9. 5/8 Fold all merge diff variants into an enumThomas Rast, Sep 6, 2014
  10. Junio C HamanoSep 8, 2014
  11. 6/8 merge-recursive: allow storing conflict hunks in indexThomas Rast, Sep 6, 2014
  12. Junio C HamanoSep 9, 2014
  13. 7/8 name-hash: allow dir hashing even when !ignore_caseThomas Rast, Sep 6, 2014
  14. Junio C HamanoSep 9, 2014
  15. 8/8 log --remerge-diff: show what the conflict resolution changedThomas Rast, Sep 6, 2014
  16. Junio C HamanoSep 8, 2014
  17. Junio C HamanoSep 9, 2014
  18. Junio C HamanoSep 9, 2014

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.