On Thu, Jul 17, 2014 at 6:23 PM, Ron W <ronw.m...@gmail.com> wrote: > The fossil export command has the options --export-marks and > --import-marks for storing and reading RIDs of exported data in a named > file. The first time you create an export to a specific, intended receiving > repo, you use just --export-marks. After that, use bothso that only the new > RIDs (since the previous export) will be exported. >
Achtung: RIDs are local to a given copy/clone of a repo, and are not eternal in nature. In theory, a rebuild can change the RIDs (though i don't think it currently does so). It is very possible that two given clones of a repo have different RIDs for the same blobs, in particular if not all work is synced (e.g. local private branches). > Some experimentation would be needed to work out a procedure for 2-way > sync via export/import, but I'm sure it could be done. > Not based on RIDs, at least not reliably. Only the UUIDs are guaranteed to be stable. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
