From: Gary Wright <gwtmp01@...>
Date: 2009-02-15T05:12:45+09:00
Subject: [ruby-core:22104] Re: A short memorandum (Re: 1.8.7 Specifics)


On Feb 14, 2009, at 2:49 PM, Charles Oliver Nutter wrote:

> Eero Saynatkari wrote:
>> 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?
>
> I don't know how to make git-svn pushable to a remote repo and  
> pushable to svn, as well as having the github clone usable by  
> everyone (though it certainly could be possible). It seems that once  
> the repo has been pushed to github, it loses its git-svn'ity, and  
> subsequent clones are no longer fully functional wrt SVN.


I'm not sure I see the problem. The only people that need bidirectional
svn access to the official Ruby SVN repo are the official maintainers
and that is done via their private (and local) git repos.

ruby-svn-repo <--> maintainer-repo  <--> github mirror --> github- 
forks <--> private repos

The maintainer uses git-svn to maintain the official ruby-svn repo and
plain old git to push to the public github mirror.  Other people
fork/clone the public repo as they wish and send pull notices to
the maintainer.  The maintainer merges changes into their private repo
from patches or pulls directly from someone else's repo at their  
discretion.

Eventually changes are committed back to the ruby-svn-repo and also  
reflected
on the master branch of the github mirror.