summaryrefslogtreecommitdiffstats
path: root/merge-recursive.c
diff options
context:
space:
mode:
authorElijah Newren <newren@gmail.com>2018-06-30 18:24:59 -0700
committerJunio C Hamano <gitster@pobox.com>2018-07-11 09:38:36 -0700
commit92702392cefdbd66ca593fa909540230ef9e005e (patch)
tree2903cd89eb8e7a0287c0f0545eaeef4aa84cc12f /merge-recursive.c
parentcf69f2af08f8dc092d57b987f26719fe0d43a40d (diff)
downloadgit-92702392cefdbd66ca593fa909540230ef9e005e.tar.gz
git-92702392cefdbd66ca593fa909540230ef9e005e.tar.xz
merge-recursive: make sure when we say we abort that we actually abort
In commit 65170c07d4 ("merge-recursive: avoid incorporating uncommitted changes in a merge", 2017-12-21), it was noted that there was a special case when merge-recursive didn't rely on unpack_trees() to enforce the index == HEAD requirement, and thus that it needed to do that enforcement itself. Unfortunately, it returned the wrong exit status, signalling that the merge completed but had conflicts, rather than that it was aborted. Fix the return code, and while we're at it, change the error message to match what unpack_trees() would have printed. Signed-off-by: Elijah Newren <newren@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'merge-recursive.c')
-rw-r--r--merge-recursive.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/merge-recursive.c b/merge-recursive.c
index 32529ca5b..2fb1bdb01 100644
--- a/merge-recursive.c
+++ b/merge-recursive.c
@@ -1984,9 +1984,9 @@ int merge_trees(struct merge_options *o,
struct strbuf sb = STRBUF_INIT;
if (!o->call_depth && index_has_changes(&the_index, &sb)) {
- err(o, _("Dirty index: cannot merge (dirty: %s)"),
+ err(o, _("Your local changes to the following files would be overwritten by merge:\n %s"),
sb.buf);
- return 0;
+ return -1;
}
output(o, 0, _("Already up to date!"));
*result = head;