Somehow I've ended up in this situation, where the parent of a commit has a newer timestamp than the child:
http://cowlark.com/cgi-bin/fossil.cgi/flooded-moon/timeline?f=905a301d7d28267ee35c41e9dd080d1ce7bcec1d Exporting this leads to the parent commit being emitted before the child commit which it references, which causes git to crash out on import. Even worse, if I try to import the export file into a new Fossil repository, it seems to work... except the repository is missing half the files! Which suggests that Fossil *should* be crashing out, but isn't. I've tried modifying the timestamp of the relevant commit, but it appears to have no effect. Suggestions? -- ┌─── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ ───── http://www.cowlark.com ───── │ "There is nothing in the world so dangerous --- and I mean *nothing* │ --- as a children's story that happens to be true." --- Master Li Kao, │ _The Bridge of Birds_
signature.asc
Description: OpenPGP digital signature
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
