On Thu, Oct 18, 2007 at 05:22:39PM -0700, Pete/Piet Delaney wrote: > I've got root access on the CVS server and want to switch to git without > disturbing the environment more than is necessary to make the switch. > I think developers will want to us git and git-cvsserver looks like > the more likely desirable path. Depending on the environment and the willingness of people to change to git, it might be worth moving slowly and keeping the backend as CVS at first. I.e., keep the "official" repository as CVS, and let some devs start moving to access through git-cvsimport and git-cvsexportcommit (and maybe even provide an official git repo which is backed by the CVS repo, so that all of the import/export happens in one place). That will give them time to get used to git, give those who are resistant to the change their original interface, and if anything goes wrong, you can always fall back to the "old" way. And then when everything seems to be going well, swap it. Make git the official repo, but provide a "legacy" CVS access for the die-hards (using git-cvsserver). And then eventually just shut off CVS access entirely (when everyone is happier using git). Of course none of that is necessary, but one of the nice things about git is how it can integrate with existing setups, so you can really ease into a transition without investing a lot of resources. -Peff - 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
