aboutsummaryrefslogtreecommitdiff
path: root/merge-recursive.c
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2017-12-06 09:09:03 -0800
committerJunio C Hamano <gitster@pobox.com>2017-12-06 09:09:03 -0800
commit2ace172f95f4afdc565bbcbc2373ebf33b8a9371 (patch)
treeac3e29bc34a5fb15b160fcc7cc3c3e53d85f0fb0 /merge-recursive.c
parent0175b6e2b9f99101b37cd4b1aa61711678a17105 (diff)
parentc641ca67072946f95f87e7b21f13f3d4e73701e3 (diff)
downloadgit-2ace172f95f4afdc565bbcbc2373ebf33b8a9371.tar.gz
git-2ace172f95f4afdc565bbcbc2373ebf33b8a9371.tar.xz
Merge branch 'sb/test-cherry-pick-submodule-getting-in-a-way' into maint
The three-way merge performed by "git cherry-pick" was confused when a new submodule was added in the meantime, which has been fixed (or "papered over"). * sb/test-cherry-pick-submodule-getting-in-a-way: merge-recursive: handle addition of submodule on our side of history t/3512: demonstrate unrelated submodule/file conflict as cherry-pick failure
Diffstat (limited to 'merge-recursive.c')
-rw-r--r--merge-recursive.c5
1 files changed, 3 insertions, 2 deletions
diff --git a/merge-recursive.c b/merge-recursive.c
index 1d3f8f0d2..9fb0b9f8f 100644
--- a/merge-recursive.c
+++ b/merge-recursive.c
@@ -1901,8 +1901,9 @@ static int process_entry(struct merge_options *o,
oid = b_oid;
conf = _("directory/file");
}
- if (dir_in_way(path, !o->call_depth,
- S_ISGITLINK(a_mode))) {
+ if (dir_in_way(path,
+ !o->call_depth && !S_ISGITLINK(a_mode),
+ 0)) {
char *new_path = unique_path(o, path, add_branch);
clean_merge = 0;
output(o, 1, _("CONFLICT (%s): There is a directory with name %s in %s. "