On Tue, Dec 17, 2013 at 3:07 PM, Eric S. Raymond <e...@thyrsus.com> wrote:
> Jakub Narębski <jna...@gmail.com>:
>> I wonder if we can add support for incremental import once, for all
>> VCS supporting fast-export, in one place, namely at the remote-helper.
> Something in the pipeline - either the helper or the exporter - needs to
> have an equivalent of vc-fast-export's and cvsps's -i option, which
> omits all commits before a specified time and generates cookies like
> "from refs/heads/master^0" before each branch root in the incremental
Errr... doesn't cvs-fast-export support --export-marks=<file> to save
progress and --import-marks=<file> to continue incremental import?
I *guess* that 'export' / 'import' capabilities-based remote helpers
use 'export-marks <file>' / 'import-marks <file>' capability for incremental
import, also known as "fetch", isn't it? But I might be mistaken, I don't
know enough about remote helpers...
I would check it in cvs-fast-export manpage, but the page seems to
It's not just you! http://www.catb.org looks down from here.
> This could be done in the wrapper, but only if the wrapper itself
> includes an import-stream parser, interprets the output from the
> exporter program, and re-emits it. Having done similar things
> myself in reposurgeon, I advise against this strategy; it would
> introduce a level of complexity to the wrapper that doesn't belong
> there, and make the exporter+wrapper combination harder to verify.
> Fortunately, incremental dump is trivial to implement in the output
> stage of an exporter if you have access to the exporter source code.
> I've done it in two different exporters. cvs-fast-export now has a
> regression test for this case
This is I guess assuming that information from later commits doesn't
change guesses about shape of history from earlier commits...
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html