On 12/12/15, org.fossil-scm.fossil-us...@io7m.com <org.fossil-scm.fossil-us...@io7m.com> wrote: > On 2015-12-12T12:26:19 +0000 > <org.fossil-scm.fossil-us...@io7m.com> wrote: >> >> Is there some way to get more information about what's going wrong here? I >> don't >> know if fossil or git is at fault, and I have no way of knowing how badly >> the >> history has been corrupted by the export or import. > > It seems that somebody else ran into this at the start of the year: > > > http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg19238.html >
Yeah, that's a bummer. Part of the problem stems from the fact that the Git fast-export format is only sparsely documented, and in some cases incorrectly documented. And Git is very fussy about the format. So it is possible to generate a fast-export file that conforms exactly to the documentation but which Git will not accept. And since Git is the dominant VCS at the moment, the Git people are under no pressure to fix this sad state of affairs. The import/export functionality of Fossil has been greatly improved in the past by the work of volunteers tracking down obscure incompatibilities. If you would like to try to get to the bottom of the problems you are seeing, and either identify the root cause, or better to suggest patches, that would be greatly appreciated. -- 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
