summaryrefslogtreecommitdiff
path: root/git-mergetool--lib.sh
diff options
context:
space:
mode:
authorLibravatar David Turner <dturner@twopensource.com>2014-05-01 20:21:09 -0400
committerLibravatar Junio C Hamano <gitster@pobox.com>2014-05-07 13:53:10 -0700
commitae352c7f37ef2098e03ee86bc7fd75b210b17683 (patch)
treedaec7c4bdaadb3f2f82a3cdfaa5189e6f5142788 /git-mergetool--lib.sh
parentGit 1.9.2 (diff)
downloadtgif-ae352c7f37ef2098e03ee86bc7fd75b210b17683.tar.xz
merge-recursive.c: fix case-changing merge bug
On a case-insensitive filesystem, when merging, a file would be wrongly deleted from the working tree if an incoming commit had renamed it changing only its case. When merging a rename, the file with the old name would be deleted -- but since the filesystem considers the old name to be the same as the new name, the new file would in fact be deleted. We avoid this by not deleting files that have a case-clone in the index at stage 0. Signed-off-by: David Turner <dturner@twitter.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'git-mergetool--lib.sh')
0 files changed, 0 insertions, 0 deletions