"Nigel Magnay" <nigel.magnay@xxxxxxxxx> writes: > I was prepared to put up with it not being a bare repository (asides > the extra /.git/ in the URL it's pretty much the same). > > On the git host I'd set refs/heads/trunk to be > ref: refs/remotes/svn/trunk > > And I'm hoping that a cron of git svn fetch ; git-update-server-info > will do the trick. It appeared to keep it in sync when I fetch > downstream. I don't know if I'm being naive though expecting that to > work as I don't grok all that git-svn needs to work properly - but I'm > working on it ;-) > > My current plan is for developers to push/pull to git to share amongst > the git-devs, and to push to svn when wanting to share with everyone > else.. > > [svn user] ---(ci/co)--->[svn] --pull--> [git] > ^ ^ > | | > push push/pull > | | > ---[git user]---- I suspect having the git users push/fetch only from svn would be more reliable. Won't there be problems if git users do merges and push to the git repo? Also, seems like it makes the transition more complicateds for git users since they have to figure out git-svn _and_ the git push/pull. Perhaps avoid the central git repo until everyone is on git. Then people have to learn not to use git-svn and to use push/pull instead. My $0.02 + seth -- Seth Falcon | seth@xxxxxxxxxxxxxxx | blog: http://userprimary.net/user/ - 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
