On Wed, Feb 11, 2015 at 7:54 AM, Richard Hipp <d...@sqlite.org> wrote:
> Fossil uses file mtimes and sizes to help it detect changes. When > your tool moves foo to foo.bak, this changes neither the mtime or the > size. So Fossil fails to detect the change, by default. But, the "new" foo.bak would have the mtime and size of the "old" foo, which would be different from the "old" foo.bak $ ls -l foo* -rw-r--r-- 1 xxx yyy 0 Feb 11 11:10 foo -rw-r--r-- 1 xxx yyy 0 Feb 11 11:09 foo.bak $ mv foo foo.bak $ touch foo $ ls -l foo* -rw-r--r-- 1 xxx yyy 0 Feb 11 11:11 foo -rw-r--r-- 1 xxx yyy 0 Feb 11 11:10 foo.bak
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
