On Sat, Dec 21, 2013 at 4:34 PM, David Given <d...@cowlark.com> wrote:
> On 21/12/13 21:24, Joerg Sonnenberger wrote: > [...] > > Yes, it certainly uses mtime by default to skip the much more expensive > > hashing step. You can disable that from the settings. > > You mean it's *supposed* not to do the SHA1 hash by default? Isn't this > horribly unsafe (because you'll miss changes, like is happening in my > case)? > The command is "fossil setting mtime-changes off". Having mtime-changes "on" (the default) means that fossil will look for changed files by only examining the size and mtime. With it "off", Fossil does a full SHA1 hash on every file in the repository. For a large repo with many files, mtime-changes "off" means that many operations are slow, because running SHA1 hashes on thousands of files takes significant time. Hence mtime-changes is "off" by default. Normally this does not cause problems, since it is very rare that a file will actually change content without either its mtime or is size changing. mtime-changes used to be "off" by default, which is manageable for projects of less than 1000 files on a fast workstation. The default got changed to "on" when people started using Fossil on larger projects. -- D. Richard Hipp d...@sqlite.org
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
