On Sat, Jun 7, 2014 at 8:03 PM, <to...@acm.org> wrote: > As for the hash mismatch this is just a minor technical issue easily > solved. The hash would have to calculated after stripping off all CRs > (Win/DOS) or converting to LFs (Macs) in text files. Then it will always > match the repo hash. >
It's unfortunately not a "minor technical issue" because of how fossil calculates the hash for the whole contents of a repository for manifest-creation (and comparison) reasons (namely its Z-card and R-card constructs). The on-disk and in-db copies have to be identical or higher-level hashing calculations which know nothing about the individual files (they just see one contiguous byte stream flying by) will have different results. > Anyway, I hope fossil wasn’t only meant to be used by fossil and sqlite > but has broader aspirations, and someone will see merit in putting this in > todo list. > Someone might see merit in it, but i'm not one of them ;). The conscious decision to use mixed-mode files is of no concern to fossil - it's not an error that files have mixed line modes, but it would be a grave error for fossil to think that it should change those for you. It would _have_ to change the copy on disk for hashing to work properly, which might destroy contents loaded in your editor or some other program. Commonly, mixed-mode is considered an error (at the developer level, not the tool level), so fossil offers to warn you if you do so, but it will not take it upon itself to convert the file for you. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
