On Sat, Jun 7, 2014 at 1:32 PM, Stephan Beal <sgb...@googlemail.com> wrote: > It's unfortunately not a "minor technical issue" because of how fossil > calculates the hash for the whole contents of a repository for > ...
The same is true for git, and Mercurial, and... It doesn't mean it can't be done, just that the VCS has to know how to canonicalize the file's contents, and that is awful. But sometimes someone has no choice. Like OS X's HFS+, which normalizes path components to NFD. Either the user, or the VCS, have to work around such problems. In the case of HFS+ that means never using characters where NFD form and the forms produced by the users' input modes differ... or having the VCS deal. In the case of CRLF vs. LF the VCS can be told to canonicalize those for specific files. (The HFS+ NFD thing first bit git years ago, and Linux Torvals ranted about it. His rant was about ZFS, which wasn't to blame -- the aborted Apple port of ZFS to OS X changed ZFS behavior to match HFS+'s. But for that he was quite right. A filesystem that does this is intolerable, especially when the Unicode form chosen happens to not match the form output by input modes most commonly (which isn't quite NFC, but usually is, at least for all Latin scripts).) Nico _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
