Nick Woolley <nickwoolley@xxxxxxxxxxx> writes: > I have script which wraps git-cvsimport and git-cvsexport, called "git-cvs". > > The main aim of the script is to automate the steps for tracking a CVS > repository with the git-cvs* commands. If I recall correctly, the above is in line with the original spirit of how git-cvsexportcommit was envisioned to be used by its original authors. That is, the import side is more or less satisfactory done in the sense that it deserved a short and sweet command name, but the export side is not as finished as the import side is, and you have to drive it more explicitly by telling what commit to send back to the CVS side. Building on top of it so the tool keeps track of what needs to be sent, like git-svn allows users to do, would be the right thing to do. > It's not currently as sophisticated as git-svn,... > ... > - Is this at all useful to anyone else in it's current form? I have to admit that it won't be to me (because I do not interact with CVS myself) but I don't count ;-) -- 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