On Wed, Oct 15, 2014 at 1:30 PM, Sean Woods <s...@seanwoods.com> wrote:
> I wish the > "gitmarks" feature was better supported in Fossil to have a true > incremental import without scripting multiple version control systems. > But, development efforts are probably better placed elsewhere. Fossil support for incremental import relys on the exporter only exporting "artifacts" newer than the previous export. I assume git can do that, but I've never used that feature. For Fossil-to-Fossil export/import, I once tested Fossil's incremental export (2 years ago so I forget the details) When exporting from Fossil, --export-marks option saves the RIDs of exported data in a file. When doing an export intended as an update to the previous export, the --import-marks option will read the saved RIDs so Fossil knows what it has already exported, then will only export data not previously exported. While this did work, we ultimately didn't need it because the IT people decided it would be "safe enough" to add a rule to the firewall permitting Fossil sync between the Test Engineering LAN and the Product Engineering LAN.
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
