Pull requests will be better, but please wait until Monday or Tuesday that we convert the account into an organizational account and turn off the replication. I'm not sure what would happen to a pull request received before we change the account status.
- Matt On Fri, Mar 25, 2011 at 11:20 PM, Mark Rada <mr...@marketcircle.com> wrote: > I've made pull request type things in the form of trac tickets, should I > make pull requests for those tickets now or leave them them as tickets? > > Sent from my iDevice > > On 2011-03-26, at 12:55 AM, Matt Aimonetti <mattaimone...@gmail.com> > wrote: > > If you were willing to contribute but didn't feel like using SVN, you can > already fork the current repo (mirror) and prepare your pull requests: > <http://help.github.com/pull-requests/> > http://help.github.com/pull-requests/ > > Basically, the switch is a technicality for most of you, but it is quite a > big change for the core team. With Xcode using git by default and Laurent > finally converting, the choice was pretty simple. Bye bye git-svn! > > We do hope to see more of you contributing now ;) > > - Matt > > On Fri, Mar 25, 2011 at 9:30 PM, Laurent Sansonetti <<lsansone...@apple.com> > lsansone...@apple.com> wrote: > >> Hi guys, >> >> We finally decided to move MacRuby's source code repository from >> subversion to Git, and GitHub seems to be the best place to do it. >> >> The move will happen somewhere this week-end, or Monday. The repository >> address will be: <https://github.com/MacRuby/MacRuby> >> https://github.com/MacRuby/MacRuby. Currently, this repository is a >> mirror of the subversion one. >> >> Here is how we will proceed: >> >> 1) Add frequent contributors to the GitHub repository. [Done] >> 2) Update the nightly build process to use the GitHub repository. [Done] >> 3) Stop the GitHub repository mirroring. >> 4) Empty the trunk branch of the subversion repository, and just keep a >> text file saying that we moved to GitHub. >> 5) Refresh the website. >> >> Once this is done, frequent contributors can commit to the central >> repository on GitHub, and MacRuby's development can continue. We will keep >> the rest of the infrastructure (such as Trac for managing the tickets), only >> the source code repository moves. >> >> If you have any suggestion or concern let us know. Also, it's possible >> that I forgot a step or two, as I'm writing this under the influence of a >> few guinness :) Hopefully Eloy or Matt will correct me. >> >> Thanks! >> Laurent >> _______________________________________________ >> MacRuby-devel mailing list >> <MacRuby-devel@lists.macosforge.org>MacRuby-devel@lists.macosforge.org >> <http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel> >> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel >> > > _______________________________________________ > MacRuby-devel mailing list > MacRuby-devel@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel > > > _______________________________________________ > MacRuby-devel mailing list > MacRuby-devel@lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel > >
_______________________________________________ MacRuby-devel mailing list MacRuby-devel@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
