aboutsummaryrefslogtreecommitdiff
path: root/git-gui/lib/commit.tcl
diff options
context:
space:
mode:
authorElijah Newren <newren@gmail.com>2017-12-21 11:19:05 -0800
committerJunio C Hamano <gitster@pobox.com>2017-12-22 12:14:16 -0800
commiteab3f2850e7cc63a8087fbeae608a1b72ea70c7b (patch)
treef9aa7db390af8ce63c23e583a4cc54ba83389303 /git-gui/lib/commit.tcl
parent3013dff8662eae06457fe6e5348dfe2270810ab2 (diff)
downloadgit-eab3f2850e7cc63a8087fbeae608a1b72ea70c7b.tar.gz
git-eab3f2850e7cc63a8087fbeae608a1b72ea70c7b.tar.xz
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 'git-gui/lib/commit.tcl')
0 files changed, 0 insertions, 0 deletions