On Sun, Nov 30, 2008 at 9:42 PM, Andrew Straw <[EMAIL PROTECTED]> wrote: > I used rsync to mirror the entire SVN repo locally and then using "git > svn clone" to import it (which took about 12 hours on a 2.5 GHz Core 2 > machine, even with the local SVN mirror). > > I haven't been able to clone the new git repo such that the 2nd git copy > would not need to do "git svn fetch" on the entire repository. Thus, it > seems that putting my git svn mirror in a publicly accessible location > isn't actually going to save anyone the pain of letting git call > subversion a bazillion times to import all history. (At least not > without me understanding things like > http://utsl.gen.nz/talks/git-svn/intro.html#howto-track-rebuildmeta )
I always use this blog post to do exactly that: http://subtlegradient.com/articles/2008/04/22/cloning-a-git-svn-clone and it works very nicely. So please publish your repository somewhere, so that others don't have to reclone the whole svn repo. Thanks, Ondrej P.S. Michael, you should learn git. :) P.P.S. Sorry I still didn't have time to port our 3D plotting from sympy to matplotlib. Seems like a lot of people would welcome that, but someone just needs to do it. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
