@matheusbsbs / matheus-bagliano / commits / 7d4aef4027
Fork 0

Documentation/git-svn: how to clone a git-svn-created repository

These instructions tell you how to create a clone of a repository created with git-svn, that can in turn be used with git-svn. Signed-off-by: Adam Roben <aroben@apple.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>

Adam Roben committed Aug 6, 2007 at 01:16 UTC 7d4aef4027e6a95fa112fa7b069f945cad294a23
1 file changed +20
Documentation/git-svn.txt
+20
@@ -435,6 +435,26 @@ Tracking and contributing to an entire Subversion-managed project
435 # of dcommit/rebase/show-ignore should be the same as above.
436 ------------------------------------------------------------------------
437
438 +The initial 'git-svn clone' can be quite time-consuming
439 +(especially for large Subversion repositories). If multiple
440 +people (or one person with multiple machines) want to use
441 +git-svn to interact with the same Subversion repository, you can
442 +do the initial 'git-svn clone' to a repository on a server and
443 +have each person clone that repository with 'git clone':
444 +
445 +------------------------------------------------------------------------
446 +# Do the initial import on a server
447 + ssh server "cd /pub && git-svn clone http://svn.foo.org/project
448 +# Clone locally
449 + git clone server:/pub/project
450 +# Tell git-svn which branch contains the Subversion commits
451 + git update-ref refs/remotes/git-svn origin/master
452 +# Initialize git-svn locally (be sure to use the same URL and -T/-b/-t options as were used on server)
453 + git-svn init http://svn.foo.org/project
454 +# Pull the latest changes from Subversion
455 + git-svn rebase
456 +------------------------------------------------------------------------
457 +
458 REBASE VS. PULL/MERGE
459 ---------------------
460