On Friday, September 21, 2018 at 9:46:47 AM UTC+2, Ralf Krapf wrote: > > Hi > There is a nasty bug in TortoiseSVN 1.10.1, Build 28295 under Win10 1803 > 64bit. > Steps to reproduce > 1. Make a new file test/text.txt in a repo > 2. Commit this file (via commit on /test/) > 3. Rename the file to Text.txt (NOT with right click -> TortoiseSVN -> > Rename, but with right click -> rename) > 4. Commit this change. Expacted behavior: under "changes made" should be > "text.txt - missing" and "Text.txt non-versioned", but it comes "No files > were changed..." >
And if it would show "missing/non-versioned": what would you do then? If you commit the "non-versioned" file, you will end up with two files with the same name that only differs in case. And the next user who does a checkout/update will have their working copy corrupted because Windows can not have two such files. That's why TSVN automatically "corrects" such renames. If you don't want TSVN to automatically save you from big mistakes, go to the settings dialog->Advanced, then set the "FixCaseRenames" to "false". *But you've been warned: this will lead to corrupted working copies if you're not very, very, very careful.* Stefan -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" 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/1d623aba-5e67-4c66-a62a-b51667aff755%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
