On 12:49 pm, screwtape@froup.com wrote:
[snip]
I believe the next step should be that somebody with the required permissions should connect to a machine on the same physical network as the SVN server and run:
time git svn clone --stdlayout --prefix="svn/" \ svn+ssh://svn.twistedmatrix.com/svn/Twisted
...then check the load on the SVN server and see if it's going to be an issue to let the clone complete. If the clone completes successfully, then (a) we know about how long it takes, and (b) we have a "seed" repository we can potentially put up for people to download. I'd be happy to download it, check it, and write up some documentation about how people should update it. If it doesn't complete successfully, we should have some helpful error messages, adjust the clone command line and try again.
Why do we need to do this again? There's already http://svn.twistedmatrix.com/git/Twisted, http://svn.twistedmatrix.com/git/Twisted2.git, and http://svn.twistedmatrix.com/git/Twisted3.git. Jean-Paul