In Windows 10 v1803 (General Release) if you have the Windows Subsystem For Linux Installed you can set a per folder attribute of SetCaseSensitiveInfo to enable case sensitivity on an NTFS File System.
https://www.tenforums.com/tutorials/111293-enable-disable-case-sensitive-attribute-folders-windows-10-a.html The quick in dirty is this command: fsutil.exe file SetCaseSensitiveInfo %CD% enable This is useful in correcting errors where a developer has checked in a file that only differs in casing but you are in Windows 10 on an NTFS File System. TortoiseSVN seems to already support this. It must be passing the underlying flag of FILE_FLAG_POSIX_SEMANTICS. I cannot seem to find any discussion of this beyond this post https://sourceforge.net/p/tortoisesvn/tickets/32/ and https://svn.haxx.se/tsvnusers/archive-2007-11/0289.shtml However unfortunately the setting is per directory and is not "sticky". Therefore when checking out a new subversion working copy TortoiseSVN still encounters tree conflicts in these scenarios until this flag is applied to the folders in question and an svn revert is performed. Would it be worth the time to implement an optional check to see if the root of the working copy has this flag set and then offer to recursively set it? This would be especially helpful on check-outs as folders are made without any user interaction per say. At very least it appears that there might be a bug where a file name who only differs in case gets deleted/replaced by TortoiseProc; I will start another topic for this shortly. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn-dev/6fc54500-e2f6-4c47-bb13-15870d823013%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
