summaryrefslogtreecommitdiff
path: root/t/t9816-git-p4-locked.sh
diff options
context:
space:
mode:
authorLibravatar Duy Nguyen <pclouds@gmail.com>2018-08-17 20:00:39 +0200
committerLibravatar Junio C Hamano <gitster@pobox.com>2018-08-17 12:10:37 -0700
commitb878579ae755e3a9d200093ced59ada3eaafb08c (patch)
treed7138412cf388250032989b8d76a7a643011773d /t/t9816-git-p4-locked.sh
parentFourth batch for 2.19 cycle (diff)
downloadtgif-b878579ae755e3a9d200093ced59ada3eaafb08c.tar.xz
clone: report duplicate entries on case-insensitive filesystems
Paths that only differ in case work fine in a case-sensitive filesystems, but if those repos are cloned in a case-insensitive one, you'll get problems. The first thing to notice is "git status" will never be clean with no indication what exactly is "dirty". This patch helps the situation a bit by pointing out the problem at clone time. Even though this patch talks about case sensitivity, the patch makes no assumption about folding rules by the filesystem. It simply observes that if an entry has been already checked out at clone time when we're about to write a new path, some folding rules are behind this. In the case that we can't rely on filesystem (via inode number) to do this check, fall back to fspathcmp() which is not perfect but should not give false positives. This patch is tested with vim-colorschemes and Sublime-Gitignore repositories on a JFS partition with case insensitive support on Linux. Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t9816-git-p4-locked.sh')
0 files changed, 0 insertions, 0 deletions