diff options
| author |  David Turner <dturner@twopensource.com> | 2014-05-01 20:21:09 -0400 |
|---|---|---|
| committer |  Junio C Hamano <gitster@pobox.com> | 2014-05-07 13:53:10 -0700 |
| commit | ae352c7f37ef2098e03ee86bc7fd75b210b17683 (patch) | |
| tree | daec7c4bdaadb3f2f82a3cdfaa5189e6f5142788 /compat | |
| parent | Git 1.9.2 (diff) | |
| download | tgif-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 'compat')
0 files changed, 0 insertions, 0 deletions