RE: [SVN-MIGRATION] Creating a git-svn copy of the repository

I think we should really focus on getting SVN up and running and making
it functional.
If after that some developers want to figure out how to bridge it to SVN
that's fine but I think we also don't want to over complicate our setup
and the message we send to contributors.

Andi

-----Original Message-----
From: Travis Swicegood [mailto:[email protected]] 
Sent: Friday, July 25, 2008 8:38 AM
To: [email protected]
Subject: [SVN-MIGRATION] Creating a git-svn copy of the repository

Hey guys;

There's been some mention of having an "official" Git repo on 
internals.  Having a repository that can be committed to increases the 
complexity, but since Git has bidirectional support to SVN, that's not 
an issue as committers can just push their changes back to SVN when 
they're ready to share.

While we don't need an official repository that people can push to, I 
think having one that they can pull from that already is connected to 
PHP's SVN server like Mono[1] would be great.  Mono claims its a two day

process to import their entire history.  Based on the size of Mono and 
my own personal experience, I would put the 270k commits to php-src at 
somewhere around 5 - 6 days worth of CPU time to import.

What's the timeline for rolling out the new SVN server for public 
consumption?  I'll be happy to help setup the Git repo, but this next 
two weeks is going to be crazy for me with a new job.

-T

[1]: http://www.mono-project.com/GitSVN

-- 
SVN Migration Project Mailing List (http://svn.php.net)
To unsubscribe, visit: http://www.php.net/unsub.php