Michael Haggerty <mhagger@xxxxxxxxxxxx> writes: > My idea is not to built (for example) cvs2git; rather, I'd like cvs2svn > to be split conceptually into two tools: > > cvs2<abstract_description_of_cvs_history>, whose job it is to determine > the most likely "true" CVS history based on the data stored in the CVS > repository, and > > <abstract_description_of_cvs_history>2svn > > Then later write > > <abstract_description_of_cvs_history>2git > <abstract_description_of_cvs_history>2hg > > etc. > > The first split is partly done in cvs2svn 2.0. And I naively imagine > that writing the new output back ends won't be all that much work. I think an intermediate interchange format is the right way to go. But, isn't this what VCP / RevML is all about? Perhaps RevML is already suited to be that interchange format... (Haven't looked at it in detail, just pointing out that there has at least been an attempt to reinvent this wheel already :-) ). -Karl - 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
