From: Eero Saynatkari <ruby-ml@...>
Date: 2009-02-15T05:21:44+09:00
Subject: [ruby-core:22105] Re: A short memorandum (Re: 1.8.7 Specifics)

Excerpts from Headius: Charles Oliver Nutter's message of Sat Feb 14 21:45:38 +0200 2009:
> 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

I think your expectations are set based on a centralized VCS?

The Github repo is just a regular old Git repo. Anyone can clone
it, make changes, and then by whatever means assigned (commit
bit/pull request/etc.) send their changes back to the *Github
repo*. Similar workflow for anyone using SVN. Neither group
will be committing to two repositories simultaneously, or be
required to do the git-svn part themselves.

The mirroring is provided by another clone. It fetches code
from both sides, manages the rebasing and keeps both updated.
This clone can be anywhere, including a "hidden" one at Github.
Of course Github might also add support for git-svn for all,
but it is not necessary for this purpose.

> Unless all three of these are easy to do and *seamless*, having the 
> repository split between github and svn is just going to add hassle. Ask 
> the Rubinius guys...they moved to git and initially hoped to have an 
> up-to-date svn mirror. It turned out to be a big hassle and they 
> abandoned the idea.

We tried it before git-svn existed, I think. And no-one missed
the SVN repo terribly.

--
Magic is insufficiently advanced technology.