> If you have access to the raw ",v" files as you do, I would suggest you > try out parsecvs. It will not do incremental imports but will you a good > idea of how you can expect the converted repository to behave / act. ParseCVS works out fine with the PHP repository for us while cvsimport has some problems with branches. For me it looks like doing parsecvs on an existing repository tries to check all ,v files but in fact producing a more or less incremental update. If you try to use parsecvs make sure that your branchname doesnot contain / or ~ as this will cause an error on parsecvs. If you need it, we have a simple patch for that with a small workaround on that. - 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
