> The problem with incremental imports is the SHA1 hash mapping between > git and Fossil: in the pure content case (blobs) they may be the same, > but the correspondence between git commits and manifest artifacts is not > currently saved anywhere. I don't think it should be too much difficult > to do though, because every other version control system does it.
My thinking was that by specifying the proper arguments to git fast-export, I was doing an incremental _export_, only capturing the changes from the previous export. In that way I thought I would avoid duplication. One [temporary, imperfect] approach might be to write a small script that reads the git export stream and imports it each commit on an open checkout, doing a `fossil commit` each time. That's obviously suboptimal, though, because we lose important metadata in the process that make the timeline view relevant. > If you have some patience, I may take a look at it once I finish testing > my import patches that generate delta manifests. Thank you very much for your response. My goal was more to gather consensus from this group rather than obtain quick turnaround on a solution (although I won't turn down a fix!) :-) I would appreciate any help you can give and am available to help or contribute in any way possible. (I've been reading the various wiki article related to internal fossil data format, but am nowhere near at the necessary level to do anything in that realm.) _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
