On 7/14/07, Michael Haggerty <mhagger@xxxxxxxxxxxx> wrote:
Incidentally, now that cvs2svn 2.0.0 is nearly out, I am thinking about what it would take to write some other back ends for cvs2svn--turning it, essentially, into cvs2xxx. Most of the work that cvs2svn does is inferring the most plausible history of the repository from CVS's sketchy, incomplete, idiomatic, and often corrupt data. This work should also be useful for a cvs2git or cvs2hg or cvs2baz or ...
Great to hear that. I'm game if we can do something in this direction - surely we can make it talk to fastimport ;-) Does cvs2svn handle incremental imports, remembering any "guesses" taken earlier? Last time I looked at it, it had far better logic than cvsps, but it didn't do incremental imports, and repeated imports done at different times would "guess" different branching points for new branches, so it _really_ didn't support incrementals cheers, m - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
