On Wed, Nov 09, 2011 at 01:39:44PM -0600, Jeffrey Ollie wrote: > On Wed, Nov 9, 2011 at 6:49 AM, Tim Allen <screwt...@froup.com> wrote: > > > > 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 > > Which will fail spectacularly because the Twisted SVN repository does > not use the standard layout that git-svn is expecting. In particular > the branches/releases and tags/releases directory will really mess > things up.
Yes, branches/releases and tags/releases would need to be specially handled; I'm not sure if it's possible to import them as just more branches and tags, or if they'd have to be removed entirely. I wouldn't call that a spectactular failure, though - you should still have trunk and the various feature branches, which is all you need to submit patches. _______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
