summaryrefslogtreecommitdiff
path: root/builtin/am.c
diff options
context:
space:
mode:
authorElijah Newren <newren@gmail.com>2017-12-21 19:19:05 (GMT)
committerJunio C Hamano <gitster@pobox.com>2017-12-22 20:14:16 (GMT)
commiteab3f2850e7cc63a8087fbeae608a1b72ea70c7b (patch)
treef9aa7db390af8ce63c23e583a4cc54ba83389303 /builtin/am.c
parent3013dff8662eae06457fe6e5348dfe2270810ab2 (diff)
downloadgit-eab3f2850e7cc63a8087fbeae608a1b72ea70c7b.zip
git-eab3f2850e7cc63a8087fbeae608a1b72ea70c7b.tar.gz
git-eab3f2850e7cc63a8087fbeae608a1b72ea70c7b.tar.bz2
t6044: recursive can silently incorporate dirty changes in a merge
The recursive merge strategy has some special handling when the tree for the merge branch exactly matches the merge base, but that code path is missing checks for the index having changes relative to HEAD. Add a testcase covering this scenario. Reported-by: Andreas Krey <a.krey@gmx.de> Signed-off-by: Elijah Newren <newren@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'builtin/am.c')
0 files changed, 0 insertions, 0 deletions