From: Thomas Rast <tr@thomasrast.ch>
To: git@vger.kernel.org
Subject: [PATCH 8/9] merge-recursive: allow storing conflict hunks in index
Date: Tue, 4 Feb 2014 23:17:37 +0100 [thread overview]
Message-ID: <adf5e5bd91a6441f0fea7412a6507ac5fd9f9a6f.1391549294.git.tr@thomasrast.ch> (raw)
In-Reply-To: <cover.1391549294.git.tr@thomasrast.ch>
Add a --conflicts-in-index option to merge-recursive, which instructs
it to always store the 3-way merged result in the index. (Normally it
only does so in recursive invocations, but not for the final result.)
This serves as a building block for the "remerge diff" feature coming
up in a subsequent patch. The external option lets us easily use it
from tests, where we'd otherwise need a new test-* helper to access
the feature.
Furthermore, it might occasionally be useful for scripts that want to
look at the result of invoking git-merge without tampering with the
worktree. They could already get the _conflicts_ with --index-only,
but not (conveniently) the conflict-hunk formatted files that would
normally be written to the worktree.
Signed-off-by: Thomas Rast <tr@thomasrast.ch>
---
Documentation/merge-strategies.txt | 5 +++++
merge-recursive.c | 4 ++++
merge-recursive.h | 1 +
t/t3030-merge-recursive.sh | 20 ++++++++++++++++++++
4 files changed, 30 insertions(+)
diff --git a/Documentation/merge-strategies.txt b/Documentation/merge-strategies.txt
index 2934e99..3468d99 100644
--- a/Documentation/merge-strategies.txt
+++ b/Documentation/merge-strategies.txt
@@ -96,6 +96,11 @@ index-only;;
Write the merge result only to the index; do not touch the
worktree.
+conflicts-in-index;;
+ For conflicted files, write 3-way merged contents with
+ conflict hunks to the index, instead of leaving their entries
+ unresolved.
+
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 f59c1d3..b682812 100644
--- a/merge-recursive.c
+++ b/merge-recursive.c
@@ -724,6 +724,8 @@ static void update_file_flags(struct merge_options *o,
int update_cache,
int update_wd)
{
+ if (o->conflicts_in_index)
+ update_cache = 1;
if (o->call_depth || o->no_worktree)
update_wd = 0;
@@ -2098,6 +2100,8 @@ int parse_merge_opt(struct merge_options *o, const char *s)
}
else if (!strcmp(s, "index-only"))
o->no_worktree = 1;
+ else if (!strcmp(s, "conflicts-in-index"))
+ o->conflicts_in_index = 1;
else
return -1;
return 0;
diff --git a/merge-recursive.h b/merge-recursive.h
index d8dd7a1..9b8e20b 100644
--- a/merge-recursive.h
+++ b/merge-recursive.h
@@ -16,6 +16,7 @@ struct merge_options {
unsigned buffer_output : 1;
unsigned renormalize : 1;
unsigned no_worktree : 1; /* do not touch worktree */
+ unsigned conflicts_in_index : 1; /* index will contain conflict hunks */
long xdl_opts;
int verbosity;
int diff_rename_limit;
diff --git a/t/t3030-merge-recursive.sh b/t/t3030-merge-recursive.sh
index 2f3a16c..4192fd3 100755
--- a/t/t3030-merge-recursive.sh
+++ b/t/t3030-merge-recursive.sh
@@ -309,6 +309,26 @@ test_expect_success 'merge-recursive --index-only' '
test_cmp expected-diff actual-diff
'
+test_expect_success 'merge-recursive --index-only --conflicts-in-index' '
+ # first pass: do a merge as usual to obtain "expected"
+ rm -fr [abcd] &&
+ git checkout -f "$c2" &&
+ test_expect_code 1 git merge-recursive "$c0" -- "$c2" "$c1" &&
+ git add [abcd] &&
+ git ls-files -s >expected &&
+ # second pass: actual test
+ rm -fr [abcd] &&
+ git checkout -f "$c2" &&
+ test_expect_code 1 \
+ git merge-recursive --index-only --conflicts-in-index \
+ "$c0" -- "$c2" "$c1" &&
+ git ls-files -s >actual &&
+ 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] &&
--
1.9.rc2.232.gdd31389
next prev parent reply other threads:[~2014-02-04 22:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-04 22:17 [PATCH 0/9] remerge diff proof of concept/RFC Thomas Rast
2014-02-04 22:17 ` [PATCH 1/9] merge-recursive: remove dead conditional in update_stages() Thomas Rast
2014-02-04 22:17 ` [PATCH 2/9] merge-recursive: internal flag to avoid touching the worktree Thomas Rast
2014-02-04 22:17 ` [PATCH 3/9] merge-recursive: -Xindex-only to leave worktree unchanged Thomas Rast
2014-02-04 22:17 ` [POC PATCH 4/9] pretty: refactor add_merge_info() into parts Thomas Rast
2014-02-04 22:17 ` [POC PATCH 5/9] log: add a merge base inspection option Thomas Rast
2014-02-04 22:17 ` [PATCH 6/9] combine-diff: do not pass revs->dense_combined_merges redundantly Thomas Rast
2014-02-04 22:17 ` [PATCH 7/9] Fold all merge diff variants into an enum Thomas Rast
2014-02-04 22:17 ` Thomas Rast [this message]
2014-02-04 22:17 ` [RFC PATCH 9/9] log --remerge-diff: show what the conflict resolution changed Thomas Rast
2014-02-04 23:04 ` [PATCH 0/9] remerge diff proof of concept/RFC Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=adf5e5bd91a6441f0fea7412a6507ac5fd9f9a6f.1391549294.git.tr@thomasrast.ch \
--to=tr@thomasrast.ch \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).