> http://blog.jthoenes.net/2011/08/01/using-git-as-frontend-for-svn/
I tried that years ago when I was still working on hornetq, and that sucked... Horrible and really complicated to use it. I would rather move to git completely. Once you get used with git you won't want to get back to svn. @Jim: It seems that you are used to SVN. Believe me.. two days after you start working with git you won't go back. With git you can do a lot more on interacting with other developers... Also: there's at least one person wanting to contribute on NMS. Moving to git will only help to build up more community around it. It's a no brainer really IMHO. Besides all projects are already in git.. I don't see a reason to keep this one on SVN. On Wed, Feb 15, 2017 at 7:25 PM, Jim Gomes <jgo...@apache.org> wrote: > So, what stops people from using Git as a front-end to Subversion and > working with the Git toolset? > > Here is a great write-up showing a developer doing just that: > > This seems like the best of both worlds. Those that want Git, can do so > without penalty (other than the huge local database). The same for those > who use Subversion. > > > On Wed, Feb 15, 2017 at 4:15 PM Timothy Bish <tabish...@gmail.com> wrote: > >> On 02/15/2017 06:41 PM, Jim Gomes wrote: >> > Breaking this out into its own discussion thread... >> > >> > It has been proposed that Apache.NMS Subversion repository be moved to a >> > Git repository. While the dominate reason seems to be "that's what >> > everyone else is doing", I'm sure there are more technical reasons for >> the >> > proposal. I will let others offer up those reasons for the move. >> > >> > As for my position, Subversion has been sufficient, but I'm not entirely >> > opposed to the move as long as certain technical requirements can be met. >> > These technical requirements can be entirely met if the Git repository is >> > automatically mirrored to GitHub, which allows for Subversion clients to >> > access a Git repository. In that case, the port to a Git repository >> > back-end would be completely transparent. >> > >> > So, let's discuss the technical merits on moving the repository to Git. >> > >> We could move to CVS, I hear some people used to think that was >> sufficient ;) >> >> Depends on who you ask about SVN vs Git. They both work, but I think >> many of us have moved on to using Git for most everything we work on so >> having to go back and muddle with SVN at this point seems an extra hurdle. >> >> I would say that having the ability to easily link a git based project >> up to the Github mirror to grab PRs, apply them, push them to my github >> mirror while testing and tweaking and them eventually merging and >> pushing to the Activemq repo is certainly a lot simpler than muddling >> with patches and SVN. >> >> It is a simple thing to have Infra mirror the NMS git repos on Github, >> we do that already with ActiveMQ, ActiveMQ-CPP and Artemis among others. >> >> -- >> Tim Bish >> twitter: @tabish121 >> blog: http://timbish.blogspot.com/ >> >> -- Clebert Suconic
