On Fri, 17 May 2013 15:14:58 +0000, Michael Haggerty wrote: ... > We both know that the CVS history omits important data, and that the > history is mutable, etc. So there are lots of hypothetical histories > that do not contradict CVS. But some things are recorded unambiguously > in the CVS history, like > > * The contents at any tag or the tip of any branch (i.e., what is in the > working tree when you check it out).
Except that the tags/branches may be made in a way that can't be mapped onto any commit/point of history otherwise exported, with branches that are done on parts of the trees first, or likewise tags. ... > That being said, I appreciate that cvsimport can do incremental imports. > cvs2git doesn't even attempt it. I've thought about what it would take > to implement correct incremental imports in cvs2svn/cvs2git, and it is Do these two produce stable output? That is, return the same commits for multiple runs on the same repo? Andreas -- "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
