It’s not pleasure work to merge the patches between the branches in SVN behind the GFW. I’m +1 for swathing cxf to git.
-- Willem Jiang Red Hat, Inc. Web: 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 January 22, 2014 at 6:02:21 PM, Sergey Beryozkin (sberyoz...@gmail.com) wrote: > > On 22/01/14 09:20, Christian Schneider wrote: > > Recently many apache projects switched from svn to git (like > Camel and > > Karaf). > > As git has many advantages compared to svn (especially for back > ports) I > > think it makes sense to also do this switch for cxf. > > > > Any opinions? > Comment from someone who has been lazy enough (scared ?) to switch > to > git completely: SVN has never caused me any issues, I mean, git > is > obviously great and much more advanced than SVN, but I haven't > found SVN > slowing down my CXF development process which is straight-forward. > > I will switch to git if that what I will need to do to work with CXF > :-), but I'm happy where I am with SVN. If that is expensive/real > hassle > to maintain, bith SVN & git repos, then sure, lets go for it > > My 2c > Sergey > > > > > > Christian > > > > >
