Michael Haggerty <mhagger@xxxxxxxxxxxx>: > Perhaps your experience is with an older version of cvs2svn? Well, it has been at least four years since I ran it on anything. Maybe that counts as old. I'm willing to believe it's working better now, but I've had to deal with geological strata of nastiness older versions produced in various Subversion repositories (cleaning up that crud was a major motivation for reposurgeon) and I'm fairly sure I haven't seen the last such fossils. Every sufficiently old Subversion repository seems to have few. > If not, > please be specific rather than just making complaints that are too vague > to be rebutted or fixed (whichever is appropriate). I put a *lot* of > effort into getting cvs2svn to run correctly, and I take bug reports > very seriously. I can't be specific now, but that may change shortly. I'm putting together a test suite for cvsps with the specific intention of capturing as many odd corner cases as I can. (I just finished writing a small Python framework for expressing interleaved CVS command sequences on multiple checkouts in a way that can be easily run.) It wouldn't be difficult for me to test whether these break cvs2svn. You've established that someone over there is paying attention, so I'll do that, I guess. I'm willing to share my test suite as well. Do you have your own zoo of odd cases I could test on? -- <a href="http://www.catb.org/~esr/";>Eric S. Raymond</a> -- 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