-1 We integrate the ActiveMQ NMS build tree into our build process using external references. Switching to Git will most likely make this impossible. If there is a solution that can continue to make this seamless for us, then I could consider changing my vote.
I would also ask what are the advantages? I see this as something that isn't broken and doesn't need fixing. Merging between branches with SVN is extremely easy, and I do it all the time. I don't understand why others complain about it. The speed for checkouts, updates and commits is excellent. On Fri, Jun 7, 2013 at 5:25 AM, Willem jiang <willem.ji...@gmail.com> wrote: > +1 and it saves you lots of time if you need to merge between the branches. > > > -- > Willem Jiang > > Red Hat, Inc. > FuseSource is now part of Red Hat > Web: http://www.fusesource.com | http://www.redhat.com > Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/) > (English) > http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese) > Twitter: willemjiang > Weibo: 姜宁willem > > > > > On Friday, June 7, 2013 at 2:25 AM, Hiram Chirino wrote: > > > Seems some other projects at the ASF have been switching from SVN to > > Git. How you guys feel about making the switch too? I know > > personally I much prefer using Git to SVN and my main development > > model has been using SVN via Git. Just want to take a poll to see if > > any of the ActiveMQ developers would have strong objections to moving > > to Git. > > > > > > -- > > Hiram Chirino > > > > Engineering | Red Hat, Inc. > > > > hchir...@redhat.com (mailto:hchir...@redhat.com) | fusesource.com ( > http://fusesource.com) | redhat.com (http://redhat.com) > > > > skype: hiramchirino | twitter: @hiramchirino > > > > blog: Hiram Chirino's Bit Mojo > > >
