from the git-svn manpage: ==== git-svn is a simple conduit for changesets between Subversion and git. It provides a bidirectional flow of changes between a Subversion and a git repository. ... Once tracking a Subversion branch (with any of the above methods), the git repository can be updated from Subversion by the fetch command and Subversion updated from git by the dcommit command. ==== If git-svn works as advertised, could we not set up a bi-directional mirror between the 1.8.6 SVN branch on ruby-lang and an "official" git repo on github maintained by Engine Yard? If this is doable, it would be a nice way for ruby-core to ease into git gradually while preserving their existing SVN infrastructure. I can't speak for Erza, but if anyone can do this, I would guess that the folks at Engine Yard can. - brent Eero Saynatkari-5 wrote: > > Excerpts from Headius: Charles Oliver Nutter's message of Sat Feb 14 > 00:53:17 +0200 2009: >> Charles Oliver Nutter wrote: >> > Urabe Shyouhei wrote: >> >> * Where to host 1.8.6 source code >> >> >> >> My recommendation is not to move from ruby-lang.org. Thanks to >> >> massive efforts made by yugui we already have a semi-automatic >> >> issue tracking on redmine.rubyu-lang.org in service. It is much >> >> easier for you to get used to that than reinvent a wheel. >> > >> > I strongly agree here. Github would be great if this were intended to >> be >> > a new branch/fork of Ruby, but since 1.8.6 is very well established it >> > would cause more trouble to move it now. It also would seem very >> strange >> > to have one branch of 1.8 on Github and others on ruby-lang. The >> > integration issues with redmine would also be a nuisance. >> >> A shorter way to say what I mean: 1.8.6 should not move without all of >> Ruby moving. I'm not opposed to Github in principal, just to having >> multiple places for ruby-core infrastructure. > > I will agree and disagree a bit: keeping the distribution at > http://ruby-lang.org (or ftp://) is expected, but I think it > is also beneficial to keep the SVN access available there. > > However, I think it is of paramount importance that there is > an *official* Git repository as well, presumably at Github. > It will result in much greater user involvement and more bug- > and --very importantly-- /documentation/ patches. > > I expect Git to be EY's preferred way of working with the > repository, but git-svn should be able to handle the other > side just fine. > > > Regards, > Eero > > -- > Magic is insufficiently advanced technology. > > > -- View this message in context: http://www.nabble.com/-ruby-core%3A21997--1.8.7-Specifics-tp21961585p22016034.html Sent from the ruby-core mailing list archive at Nabble.com.