Hi Robert, The change is not a matter of code size, is more how it will affect your current workflow, for example if you keep accepting patches one by one, and they made to the repository one by one there will be now difference, and no extra problems, with the current workflow. If you switch to the "modern" pull from other sources, new branches by features, and multiple and complex merges, then that will affect your current workflow.
Github encourage contributors to fork first, change, and notify changes to master branch, that's the "git" way of working. But you can keep your own way, accepting patches only by mail, in that case there will be no difference with your current subversion workflow. Cheers, JL On Fri, Jan 13, 2012 at 4:53 PM, Robert Osfield <[email protected]> wrote: > Hi Mathieu, > > On 11 January 2012 18:01, Mathieu MARACHE <[email protected]> wrote: >> I used git before our internal repo moved from subversion to git, with >> git-svn that allows to commit back to a svn repo, here is a page that >> explains the process : >> http://www.codeography.com/2010/03/17/howto-mirror-git-to-subversion.html > > Thanks for the link. > > I've now subscribe to github, my username is robertsofield. > > Over the next couple of weeks I'll work on clearing the > osg-submissions backlog to the present svn repository and learn git a > little at the same time, then we can look at the possibility of moving > OpenSceneGraph across as using github as the main repository. It > might be sensible to try out moving VirtualPlanetBuilder across first > as it's smaller code and userbase wise. > > Thoughts? > Robert. > _______________________________________________ > osg-users mailing list > [email protected] > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org -- Jose L. Hidalgo Valiño (PpluX) ---- http://www.pplux.com ---- _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
