Fossil: View Ticket

2013-10-26
21:38		• Ticket [4b881458c3] support for incremental import/export status still Open with 3 other changes ... (artifact: c0989f5519 user: anonymous)
2011-09-12
13:19		• Ticket [4b881458c3]: 2 changes ... (artifact: 7ead063746 user: joerg)
2011-09-11
17:11		• Closed ticket [0dddfe5d22]: incremental update of git export plus 2 other changes ... (artifact: 0f1df4adb3 user: dmitry)
2011-02-11
09:38		• New ticket [4b881458c3] support for incremental import/export. ... (artifact: b383a0ed3e user: anonymous)

Ticket Hash:	4b881458c3b93b88e7d7b3666162ba17711fe7fe
Title:	support for incremental import/export
Status:	Open	Type:	Feature_Request
Severity:		Priority:
Subsystem:		Resolution:	Open
Last Modified:	2013-10-26 21:38:34 12.43 years ago	Created:	2011-02-11 09:38:10 15.14 years ago
Version Found In:

Description:
According to the post which I sent to the mailing list, I believe it would be nice if Fossil would extend its current support for import/export from/to Git by adding support for incremental import/export according to the Git's fast-import/export docs: --export-marks=<file> Dumps the internal marks table to <file> when complete. Marks are written one per line as :markid SHA-1. Frontends can use this file to validate imports after they have been completed, or to save the marks table across incremental runs. As <file> is only opened and truncated at checkpoint (or completion) the same path can also be safely given to --import-marks. --import-marks=<file> Before processing any input, load the marks specified in <file>. The input file must exist, must be readable, and must use the same format as produced by --export-marks. This would (hopefully) enable Fossil users to keep using Fossil while collaborating with other SCM systems, something what one can e.g. achieve with Bazaar by using bzr-{hg,git,svn} plugins. joerg added on 2011-09-12 13:19:30 UTC: "fossil export" supports marker files. It doesn't work reliably for git though as it tends to fail on the git side during testing. It was complaining about missing objects, which are clearly part of an earlier import.
User Comments:
anonymous added on 2013-10-26 21:38:34: I would like to bump this up. It's been two years and even incremental import from git (or git bundles, which can be offset from a tag/rev/time offset) would be most useful.