Ok, here's something for testers and/or documentation people: I wrapped a little script around cvs2git (which I imported from the git tools thing), and now you can do git cvsimport <cvsroot> <modulename> and it might all "just work". Right now the little sript is actually being anal and checking that CVSROOT is a directory, even though I think it all _should_ work even if CVSROOT is remote too. But I don't have any remote things to test, and for all I know maybe performance is horrible, so for now it artificially limits it to locally accessible CVS repos. I'd love it if somebody tested the remote case (and, if it works, sends me a patch that just removes the anal tests in git-cvsimport-script), and maybe even updated the information a bit more.. As it is, that Documentation/cvs-migration.txt file is a bit on the light side. Finally, I don't know what to do about cvsps options. It seems that the default time-fuzz is a bit too long for some projects, so at least that one should be overridable. So my silly script is not exactly wonderful, but I think it's more approachable than people doing the magic by hand (and forgetting to set TZ to UTC and the "-A" flag etc etc). Linus - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.htmlReceived on Wed Jun 08 09:02:45 2005
This archive was generated by hypermail 2.1.8 : 2005-06-08 09:02:48 EST