the only show stopper I know is for svn trunk which contains a lot of components
so -1 for plugins, shared, skins, resources but no problem for me for other release roots containing only one component [1] notice I don't see much gain: did we get much patches for components already in git? did nobody send a patch through github for a svn component replicated to github? Is everybody fluent with git (I still ses much "merge" commits in git) So what's the rationale, really? (apart from bashing one scm over the other, in one or another direction) So I'm -0 on such a change for parts where I feel it would be feasible Regards, Hervé [1] https://builds.apache.org/view/M-R/view/Maven/job/dist-tool-plugin/site/dist-tool-check-source-release.html Le mercredi 12 février 2014 22:37:36 Jason van Zyl a écrit : > Can we start the process of converting everything to Git. I don't really see > any benefit in using Subversion any longer. > > If so then we should just get together for a day and convert them and then > get infra to use what we converted to do the flip. > > Jason (who would be happy to never execute svn again) > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
