If a commit was run after every round-trip to the server, the artifacts would be preserved, and only a rebuild would be needed to bring the repository to a stable state (with potentially very large phantom/orphan tables). A future sync/pull should in that case continue the operation without a problem. All that needs to be done (if I am right) is to mark the repository as "mid-sync" or some such, and on the next access either continue the sync or force a rebuild.
On Sun, Sep 9, 2012 at 6:58 PM, Rene <renew...@xs4all.nl> wrote: > On 2012-09-09 17:30, Baruch Burstein wrote: > >> Would it be possible to do partial clones/syncs? It seems that by the >> definition of a fossil repository this should be trivial (receiving >> artifacts in any order). I am asking because It took me a few days to >> successfully clone >> http://netbsd.sonnenberger.**org/<http://netbsd.sonnenberger.org/>[1] on a >> bad >> >> connection. A few times I had already gotten over 1GB, and it was all >> lost when the clone couldn't be completed. >> > That is a big repository! > I don't think it is possible to have clone continue its operation where it > was so rudely interrupted! > -- > Rene > ______________________________**_________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.**org <fossil-users@lists.fossil-scm.org> > http://lists.fossil-scm.org:**8080/cgi-bin/mailman/listinfo/**fossil-users<http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users> > -- ˙uʍop-ǝpısdn sı ɹoʇıuoɯ ɹnoʎ 'sıɥʇ pɐǝɹ uɐɔ noʎ ɟı
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
