Hi All, Just something I noticed that seems un-intuitive and makes calling the binary from something like PHP more difficult. The "--nochange" option is documented as "do not perform changes but show what would be done" so it really shouldn't change _FOSSIL_. If you don't have write permission to _FOSSIL_ you can get the following error:
steve@VaioLx:~/sandbox/research/repo/work$ fossil update trunk --nochange fossil: SQLITE_READONLY: statement aborts at 39: [UPDATE vfile SET mtime=(SELECT mtime FROM vfile WHERE id=:idv) WHERE id=:idt] attempt to write a readonly database fossil: SQL error: attempt to write a readonly database I am not quite sure why it would update the timestamp for a dry run. Maybe that code can be bypassed with the "--nochange" option. -Steve
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
