doeetj...@gmail.com writes: > Hello ! > We are using Subversion in our company for a decade now. A few > developers have already switched to Git via git-svn, i.e. everyone has > one's own bridge to send and receive changes. > Unfortunately, it's not possible to shut down our SVN server and > migrate the whole team to Git in the foreseeable future. > > I'm now thinking of a solution for creating a central bridge or a > gateway, so Git users can submit their changes to some central Git > repository which is synchronised with central SVN repository. > > After googling available solutions I came up with this list: > > 1. git-as-svn > https://github.com/bozaro/git-as-svn > > 2. git-svn-bridge > https://github.com/mrts/git-svn-bridge > > 3. subgit > http://subgit.com > > Does anyone here have experience with any of those three? Any other > recommendations? > I'll appreciate your reply, and thanks in advance !
I can heartily recommend subgit. It's my solution for SVN whenever I encounter it. In some places I've had to sneak it in, and no one noticed what was happning, except that I was significantly more happy when working :) In other places it's been in place before I arrived. It is rather easy to set up and maintain. Though I have to add that I've only ever used it on SVN repos that used a standard Trunk/Tags/Branches layout. /M -- Magnus Therning OpenPGP: 0x927912051716CE39 email: mag...@therning.org jabber: mag...@therning.org twitter: magthe http://therning.org/magnus What one programmer can do in one month, two programmers can do in two months. — Fred Brooks -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: PGP signature
