because hashed files were previously stored in lower case, i had to upgrade the hashing version to 3. version 2 trees will be imported when upgrading to version 3, but not the file registry.
renaming should occur in the following situations:
- duplicates caused by directory merging.
- files that share the same name in a case-insensitive context but that are actually different in a case-sensitive context.
todo:
- directories that share the same name in a case-insensitive context but that are actually different in a case-sensitive context. this may have to be more contrived than file renaming; hopefully it's a less common situation...
it hasn't been well tested, so various share operations might break. i have been testing on Windows, on which support for a case-sensitive file system is minimal; feedback from Linux devs is very welcome to see how this can be improved.
implemented renaming in rev 3156.
because hashed files were previously stored in lower case, i had to upgrade the hashing version to 3. version 2 trees will be imported when upgrading to version 3, but not the file registry.
renaming should occur in the following situations:
- duplicates caused by directory merging.
- files that share the same name in a case-insensitive context but that are actually different in a case-sensitive context.
todo:
- directories that share the same name in a case-insensitive context but that are actually different in a case-sensitive context. this may have to be more contrived than file renaming; hopefully it's a less common situation...
it hasn't been well tested, so various share operations might break. i have been testing on Windows, on which support for a case-sensitive file system is minimal; feedback from Linux devs is very welcome to see how this can be improved.