From e9bfa9b2c97714ddb520595db729bcad416ce1d3 Mon Sep 17 00:00:00 2001 From: Junio C Hamano Date: Tue, 7 Aug 2007 06:06:11 +0000 Subject: [PATCH] Autogenerated HTML docs for v1.5.3-rc4-24-g5b56a --- git-svn.html | 21 ++++++++++++++++++++- git-svn.txt | 20 ++++++++++++++++++++ 2 files changed, 40 insertions(+), 1 deletion(-) diff --git a/git-svn.html b/git-svn.html index 6f33ba71c..0735891f4 100644 --- a/git-svn.html +++ b/git-svn.html @@ -931,6 +931,25 @@ section because they affect the git-svn-id: metadata line.

# You may only dcommit to one branch/tag/trunk at a time. The usage # of dcommit/rebase/show-ignore should be the same as above. +

The initial git-svn clone can be quite time-consuming +(especially for large Subversion repositories). If multiple +people (or one person with multiple machines) want to use +git-svn to interact with the same Subversion repository, you can +do the initial git-svn clone to a repository on a server and +have each person clone that repository with git clone:

+
+
+
# Do the initial import on a server
+        ssh server "cd /pub && git-svn clone http://svn.foo.org/project
+# Clone locally
+        git clone server:/pub/project
+# Tell git-svn which branch contains the Subversion commits
+        git update-ref refs/remotes/git-svn origin/master
+# Initialize git-svn locally (be sure to use the same URL and -T/-b/-t options as were used on server)
+        git-svn init http://svn.foo.org/project
+# Pull the latest changes from Subversion
+        git-svn rebase
+

REBASE VS. PULL/MERGE

@@ -1004,7 +1023,7 @@ should be manually entered with a text-editor or using
diff --git a/git-svn.txt b/git-svn.txt index 0a210e4be..816340b94 100644 --- a/git-svn.txt +++ b/git-svn.txt @@ -435,6 +435,26 @@ Tracking and contributing to an entire Subversion-managed project # of dcommit/rebase/show-ignore should be the same as above. ------------------------------------------------------------------------ +The initial 'git-svn clone' can be quite time-consuming +(especially for large Subversion repositories). If multiple +people (or one person with multiple machines) want to use +git-svn to interact with the same Subversion repository, you can +do the initial 'git-svn clone' to a repository on a server and +have each person clone that repository with 'git clone': + +------------------------------------------------------------------------ +# Do the initial import on a server + ssh server "cd /pub && git-svn clone http://svn.foo.org/project +# Clone locally + git clone server:/pub/project +# Tell git-svn which branch contains the Subversion commits + git update-ref refs/remotes/git-svn origin/master +# Initialize git-svn locally (be sure to use the same URL and -T/-b/-t options as were used on server) + git-svn init http://svn.foo.org/project +# Pull the latest changes from Subversion + git-svn rebase +------------------------------------------------------------------------ + REBASE VS. PULL/MERGE --------------------- -- 2.26.2