On Sat, Dec 21, 2013 at 09:21:25PM +0000, David Given wrote: > I have found a rather unpleasant-looking bug where if a file's content > changes too quickly, and its size does not change, it's not considered > to have changed. It smells as if Fossil is using a combination of the > file length and timestamp to determine whether the file has changed.
Yes, it certainly uses mtime by default to skip the much more expensive hashing step. You can disable that from the settings. Joerg _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
