From: Eero Saynatkari <ruby-ml@...>
Date: 2009-02-15T04:58:47+09:00
Subject: [ruby-core:22103] Re: A short memorandum (Re: 1.8.7 Specifics)

Excerpts from Eero Saynatkari's message of Sat Feb 14 21:15:53 +0200 2009:
> Excerpts from Headius: Charles Oliver Nutter's message of Sat Feb 14 20:49:52 +0200 2009:
> > Eero Saynatkari wrote:
> > > 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.
> > 
> > In any case, since there's no realistic way to mirror a github repo from 
> > SVN, 
> 
> What makes you say that? For reference, here is the git-svn
> manpage:
> 
>     http://www.kernel.org/pub/software/scm/git/docs/git-svn.html
> 
> Or is there some other issue I am not aware of? Properties?

After discussion I realise I misunderstood Charles' point here:
to avoid confusion, here is how it works:

1. Import code from SVN trunk to the Git repo.
2. You now have bidirectional access to the SVN repo.

Then either one could be treated as the "master." It is only
a matter of convention and documentation. There is no need
to destroy the SVN and then recreate it to track the Git
somehow--and this probably not be easy/possible.


--
Magic is insufficiently advanced technology.