From: Brent Roman <brent@...>
Date: 2009-02-15T05:33:13+09:00
Subject: [ruby-core:22106] Re: A short memorandum (Re: 1.8.7 Specifics)


Charlie,

I'll defer to the git experts regarding whether a true bidirectional conduit
is possible on a remote repository.

However, in this case, while the designated maintainer manages all commits
to the 1.8.6 SVN branch, is a true bidirectional conduit really necessary? 
I mean, practically speaking, if Engine Yard is responsible for the 1.8.6
branch, no one else should be checking in to it without their consent. 
Correct?

So, why do we need to support non-maintainers "pushing to SVN" for that
branch?

I guess this would imply that all those pushing patches into 1.8.6 the would
have to agree to use git to do so.  Others just following the HEAD could
choose to use SVN or git.

There are some real advantages to using git to support external
collaboration, etc., but switching all of ruby-core over at once is a
non-starter.  I think this might be a good opportunity to ease into it.

- brent


Charles Oliver Nutter-2 wrote:
> 
> 
> git-svn works great on a local repository (I use it myself), but I know 
> of nobody (including myself) that's been able to push a repo to github 
> and have it remain git-svn-enabled. Of course, I'm no git expert, and if 
> it's possible to have a repo setup that fills all these needs, I'd love 
> to see it:
> 
> * Must support pushing to github
> * Must support pushing to SVN
> * Must be ready-to-go or easy to make ready-to-go for SVN pushing after 
> a clone from github
> 
> An official one-way mirror to github is certainly fine, and I have no 
> strong opinion about a complete move to github. But please, no split 
> repository, especially not for just 1.8.6.
> 
> - Charlie
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/-ruby-core%3A21997--1.8.7-Specifics-tp21961585p22016664.html
Sent from the ruby-core mailing list archive at Nabble.com.