Richard, Thank you for the details. I just realized that the check-in date may be altered via "fossil amend --date" or from UI via check-in's edit submenu. This will add the tag "date=<new-timestamp>" and update the check-ins MTIME.
Looks like both timeline and export indeed pick up the updated MTIME. I looked up the sqlite's cases that crashed export (655991ec8a781d67, 1ef0dc9328f47506) and both seem to have a corrected date tag, yet the corresponding event.MTIME is not updated, i.e. MTIME=OTIME. That's why this had no expected effect. I guess, it's on purpose as you mentioned, for testing. No changes made to the remote repo. When these are updated locally, the export completes successfully. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
