Hi,
Every time I open a fossil repo, even if I simply open it to just get a copy
of the files in some directory, I end up with a 'touched' repo file, as if
some 'write' operation has occurred in the database. And a binary compare
of before and after shows that some bytes actually change. However, if
there are no commits, or any of the other operation that would normally
write into the SQLite database, why is the database file updated at all? Is
this 'writing' a necessity for fossil's normal operation, or is it something
that could be avoided by improving fossil?
Why is this a nuisance? Because software that automatically backs up files
based on their having been touched since last time will backup those files
even when they haven't changed at all (from a logical point of view, even if
something is actually written in them, it seems to be irrelevant as they
will behave the same as the version before the 'write' occurred.)
Thanks.
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
