Hi, On Mon, 23 Jul 2007, Steffen Prohaska wrote: > What's a reasonable workflow when some people use git and other people > use git-cvsserver simultaneously? This is what we did here: We cvsimported the whole stuff (but we did not have your problems, since there was only one branch). Then we initialised a shared repository with that branch, turned on git-cvsserver (and found a few bugs, but that was long ago, and AFAIR all our issues were fixed) and went to work. There were a few committing via cvs, and a few others committing via git. One person only tracked via cvs, not contributing code, just reviewing and testing. We did not have the need to impose certain restrictions, such as git-shell (to prevent invoking other programs), or hooks refusing a push that touches parts the person pushing has no business changing. But we had the option to go there, if needed. So far, all went fine. And I'm convinced that it is partly because of the trust model. After all, I still have my local repository. And that I can trust at all times. So if a poisonous person (instead of thrashing the mailing list with long mails) would have decided to corrupt the repo, we would have realised that pretty quickly, repaired the damage without much effort, and kicked out that person. Needless to say that all our devs converted to Git. And I'm happy to say that they're all happy with it. Ciao, Dscho - 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
