On Sun, Dec 7, 2014 at 12:35 PM, Stephan Beal <sgb...@googlemail.com> wrote: > On Sun, Dec 7, 2014 at 6:55 PM, <to...@acm.org> wrote: >> >> The problem: A (mostly) text file with just a few normally non-text chars >> which confuse fossil into thinking the whole file is binary. > > > There's an irony in there somewhere. It can't be partly binary, it is either > entirely binary or not binary. i.e. 0 or 1. There is no middle ground (in > the world of integers).
A VCS shouldn't have to know the contents' type, not for the purpose of versioning the file, except that: - for diff presentation purposes it helps to know - there may be many delta algorithms to choose from, and the contents' type might help choose one Picking a default sanely is a useful thing to do; an 80/20 heuristic is needed. If the heuristic can be cheaply fine-tuned to be 90/10, so much the better. When the heuristic fails the user should be able to tell the VCS what the content type is. Whatever content type is set (even if heuristically determined) should be "sticky", even if a subsequent commit introduces contents that yields a different heuristically-determined content type. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
