On Wed, May 05, 2021 at 09:23:05AM +0900, Junio C Hamano wrote: > Torsten Bögershausen <tboegi@xxxxxx> writes: > > > To my undestanding we try to rename > > foo/ into FOO/. > > But because FOO/ already "exists" as directory, > > Git tries to move foo/ into FOO/foo, which fails. > > > > And no, the problem is probably not restricted to MacOs, > > Windows and all case-insenstive file systems should show > > the same, but I haven't tested yet, so it's more a suspicion. > > > > The following diff allows to move foo/ into FOO/ > > If someone wants to make a patch out if, that would be good. > > Is strcasecmp() sufficient for macOS whose filesystem has not just > case insensitivity but UTF-8 normalization issues? > Strictly speaking: no. The Git code doesn't handle UTF-8 uppper/lower case at all: git mv bar.txt BAR.TXT works because strcasecmp() is catching it. git mv bär.txt BÄR.TXT needs the long way: git mv bär.txt baer.txt && git mv baer.txt BÄR.TXT We have been restricting the case-change-is-allowed to ASCII filenames all the time. There is no information, which code points map onto each other in Git, since this is all file system dependent. NTFS has one way, HFS+, APFS another, VFAT a third one, and if I expose ext4 via SAMBA we probably have another one. Not mentioniong that ext4 can be use case-insensitve on later Linux kernels, which sticks to unicode. Or Git repos running on machines using ISO-8859-1, those should be rare these days. That said, people are renaming files in ASCII only and are happy, and in that sense renaming directories in ASCII can be supported without major hassle. And the inode approach mentioned as well: This could go on top of strcasecmp() to cover non-ASCII filenames or other oddities, if someone implements it.
