On Thu, 12 Dec 2013 08:42:25 +0000, Martin Langhoff wrote:
> - run a cvs to git import at time T, resulting in repo G
> - make commits to cvs repo
> - run cvs to git import at time T1, pointed to G, and the import tool
> will only add the new commits found in cvs between T and T1.
I'm pretty sure that being given only G the incremental approach wouldn't
work - some extra state would be required.
But anyway, the replacement question is a) how fast the cvs-fast-export is
and b) whether its output is stable, that is, if the cvs repo C yields
a git repo G, will then C with a few extra commits yield G' where every
commit in G (as identified by its SHA1) is also in G', and G' additionally
contains the new commits that were made to the CVS repo.
If that is the case you effectively have an incremental mode, except that
it's not quite as fast.
At least that would be good enough for us - we ended up running a
filter-branch on the resulting history, and that takes some time anyway.
> The cvsimport+cvsps combo does a reasonable (though imperfect) job on
> 'flying fish' CVS histories _and that is what most projects evolved to
> use_. If other cvs import tools can handle crazy histories, hats off
> to them. But careful with knifing cvsps!
It won't magically disappear from your machine, and you have been warned. :-)
"Totally trivial. Famous last words."
From: Linus Torvalds <torvalds@*.org>
Date: Fri, 22 Jan 2010 07:29:21 -0800
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