On Thu, 12 Jun 2008 01:38:43 -0400, MenTaLguY wrote:
On Thu, 2008-06-12 at 00:36 -0400, Jeff Kowalczyk wrote:
BTW, my bzr trunk is here for those who are interested:
I presume SF makes a backup of the svn repository available to admins. git (and/or bzr) svn clone might run much better from a file:// URL. After that, the remote URL could be set back to SF https://.
I've done that, it certainly does work better. The main issue is that the URL gets baked into the imported history, so it is unsuitable for use with git-svn to commit back to SVN. (Though it is possible, with some custom software, to rewrite the imported history to get around that.)
It sounds like rewriteRoot would help:
http://www.kernel.org/pub/software/scm/git/docs/git-svn.html
svn-remote.<name>.rewriteRoot
This allows users to create repositories from alternate URLs. For example, an administrator could run git-svn on the server locally (accessing via file://) but wish to distribute the repository with a public http:// or svn:// URL in the metadata so users of it will see the public URL.
Since the noMetadata, rewriteRoot, useSvnsyncProps and useSvmProps options all affect the metadata generated and used by git-svn; they must be set in the configuration file before any history is imported and these settings should never be changed once they are set.
Additionally, only one of these four options can be used per-svn-remote section because they affect the git-svn-id: metadata line.