summaryrefslogtreecommitdiff
path: root/t/t4101/diff.0-2
diff options
context:
space:
mode:
authorLibravatar Elijah Newren <newren@gmail.com>2017-12-21 11:19:07 -0800
committerLibravatar Junio C Hamano <gitster@pobox.com>2017-12-22 12:20:38 -0800
commit65170c07d466b18364e0d2b6a360900c073b600f (patch)
treea49f75c8833813cf08d9c6b81a3bc4f6c7eafd24 /t/t4101/diff.0-2
parentmove index_has_changes() from builtin/am.c to merge.c for reuse (diff)
downloadtgif-65170c07d466b18364e0d2b6a360900c073b600f.tar.xz
merge-recursive: avoid incorporating uncommitted changes in a merge
builtin/merge.c contains this important requirement for merge strategies: /* * At this point, we need a real merge. No matter what strategy * we use, it would operate on the index, possibly affecting the * working tree, and when resolved cleanly, have the desired * tree in the index -- this means that the index must be in * sync with the head commit. The strategies are responsible * to ensure this. */ merge-recursive does not do this check directly, instead it relies on unpack_trees() to do it. However, merge_trees() has a special check for the merge branch exactly matching the merge base; when it detects that situation, it returns early without calling unpack_trees(), because it knows that the HEAD commit already has the correct result. Unfortunately, it didn't check that the index matched HEAD, so after it returned, the outer logic ended up creating a merge commit that included something other than HEAD. Signed-off-by: Elijah Newren <newren@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t4101/diff.0-2')
0 files changed, 0 insertions, 0 deletions