On Fri, Aug 9, 2013 at 9:33 AM, j. van den hoff <[email protected]>wrote:
> > I guess the problem might be related to `fossil' checking `mtime' with a > too low time resolution. is this possible? it is of course irrelevant for > interactive use but not so for scripts like this one. > The default behavior is for Fossil to check both stat.st_mtime and stat.st_size. If either change, then the file is assumed to have changed. You can run "fossil setting mtime-changes off" and then Fossil will also compare the files byte-by-byte looking for changes. "mtime-changes" is on by default because under normal operation, the mtime always changes with an update and doing byte-by-byte comparisons for every file in a large project is slow. The byte-by-byte comparisons are really only necessary when doing lots of check-ins from a script, as you are doing. -- D. Richard Hipp [email protected]
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
