Hi there! I've been playing around with git for a while, read the guides to git-svn and have been successfully using it on my own to track an upstream svn repository. Eventually, I'd like us all to switch to git, throw out the svn server, and replace it with a git repository that can be pushed to, where commits that pass tests get merged into the master. But - that's not going to happen overnight. The most likely next steps are going to be something like migrating a couple of other developers onto git to test the water, but in the interim most people will still be on svn. Has anyone got any tips as I'm sure it's a path trodden before? I've seen examples of keeping a read-only svn, but that's not really what I'm after. I'm considering whether to have a central git repo regularly pull from svn so that it's up to date, and having us possibly push to svn (or git if it's not merged to trunk) as an interim step.. Nigel - 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
