From: Stephen Bannasch Date: 2011-01-08T05:58:47+09:00 Subject: [ruby-core:34238] Re: Moving to Git? At 5:37 AM +0900 1/8/11, Lucas Nussbaum wrote: >On 08/01/11 at 05:13 +0900, Ryan Davis wrote: >> >> On Jan 7, 2011, at 12:02 , Daniel Bovensiepen wrote: >> >> > - new people would be committing work to Ruby if we switch to git >> > -> is this really true? how much stuff is coming back via the current git-mirror on github? >> >> DATA: There are a whopping FIVE pull requests on github.com/ruby/ruby (including closed). There are only three on shyouhei's (including closed). >> >> So, no, not really, despite there being 97 forks of ruby on github. >> >> Again, I think this is a family matter and the rest of the contributors on this thread are git zealots pushing an agenda more than a necessary solution. > >Is it really a good indicator? No. With the current setup (main repo in svn, official git clone) I'd use these steps: Clone the ruby git repo and develop a patch in a local branch, create a patch and attach it to a redmine issue. If the patch was more involved I'd fork the ruby git repo on github push my local feature branch to my fork, publicize my fork/feature-branch to other folks interested in evaluating the patch -- but still submit the changes as a patch suitable for integration via subversion by a committer. Making a git or github pull request doesn't make much sense because source flows one way from subversion repo to official git clone. If the main repo *was* git then pull request would make sense.