On Sun, Jun 17, 2018 at 10:08 PM Warren Young <war...@etr-usa.com> wrote:
> On Jun 17, 2018, at 2:05 PM, Warren Young <war...@etr-usa.com> wrote: > > > > If you’re willing to gamble that if the first test returns true that the > second will also returns true, it buys you a big increase in speed. The > gamble is worth taking as long as the files’ modification timestamps are > trustworthy. > > I just remembered something: “fossil up” purposely does not modify the > mtimes of the files it writes to match the mtime of the file in the > repository because it can cause difficult-to-diagnose build system errors. > Writing changed files out with the current wall time as the mtime is more > likely to cause correct builds. > To that i'm going to add that fossil doesn't actually store any file timestamps! It only records the time of a commit. When fossil is asked "what's the timestamp for file X?", the answer is really the timestamp of the last commit in which that file was modified. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ "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
