Junio C Hamano wrote: > 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. Ok - thanks. Apart from fixing significant bugs, for now I've been avoiding making any major changes to git-cvsexportcommit git-cvsimport, since understanding their guts takes a significant amount of time and effort. On the other hand, if I ever did, then currently git-cvsexportcommit and git-cvsimport are separate commands. I would imagine they would want to share some code, like "push" and "pull" operations do in git-cvs. Is that possible/encouraged in the current scheme? (e.g. "use Git::CVS" - I notice there is a Git.pm in the source.) Or would this need to be done by rolling it all into a single command as git-svn seems to do it? >> - 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 ;-) An enviable position to be in, sir. N -- 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