On 12 Oct 2007, at 4:36:29 PM, mfwitten@xxxxxxx wrote:
To make things simple, I think all of the necessary machinery should be put into git-cvsimport. The user should first git-cvsexportcommit as necessary.
Now that I have considered, it makes more sense to put the machinery in git-cvsexportcommit. The user could use a -b flag to specify the git branch to push into after the cvs commit occurs, and git-cvsexportcommit would update the .git/SCM_IMPORT file (changed from CVS_IMPORT). Of course, this introduces other troubles. Sometimes I run cvsexportcommit using a git repo on another server. So perhaps one should also be able to use cvsexportcommit for just pushing and editing the .git/SCM_IMPORT file. That way it's possible to update CVS and then notify any other git repo by hand. Michael - 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
