Autogenerated HTML docs for v1.5.3-rc4-24-g5b56a

diff --git a/git-svn.html b/git-svn.html
index 6f33ba71c678f1bbb79e895a6187bcb8fc5dba36..0735891f48d5c933f595b6e7706d412e1afbe8de 100644 (file)
--- a/git-svn.html
+++ b/git-svn.html
@@ -931,6 +931,25 @@ section because they affect the <em>git-svn-id:</em> metadata line.</p>
 # You may only dcommit to one branch/tag/trunk at a time.  The usage\r
 # of dcommit/rebase/show-ignore should be the same as above.</tt></pre>\r
 </div></div>\r
+<p>The initial <em>git-svn clone</em> can be quite time-consuming\r
+(especially for large Subversion repositories). If multiple\r
+people (or one person with multiple machines) want to use\r
+git-svn to interact with the same Subversion repository, you can\r
+do the initial <em>git-svn clone</em> to a repository on a server and\r
+have each person clone that repository with <em>git clone</em>:</p>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt># Do the initial import on a server\r
+        ssh server "cd /pub &amp;&amp; git-svn clone http://svn.foo.org/project\r
+# Clone locally\r
+        git clone server:/pub/project\r
+# Tell git-svn which branch contains the Subversion commits\r
+        git update-ref refs/remotes/git-svn origin/master\r
+# Initialize git-svn locally (be sure to use the same URL and -T/-b/-t options as were used on server)\r
+        git-svn init http://svn.foo.org/project\r
+# Pull the latest changes from Subversion\r
+        git-svn rebase</tt></pre>\r
+</div></div>\r
 </div>\r
 <h2>REBASE VS. PULL/MERGE</h2>\r
 <div class="sectionbody">\r
@@ -1004,7 +1023,7 @@ should be manually entered with a text-editor or using
 </div>\r
 <div id="footer">\r
 <div id="footer-text">\r
-Last updated 19-Jul-2007 02:09:56 UTC\r
+Last updated 07-Aug-2007 06:05:54 UTC\r
 </div>\r
 </div>\r
 </body>\r

diff --git a/git-svn.txt b/git-svn.txt
index 0a210e4bea49d49e9d38de402cc355ed4acc6a71..816340b9440cb5acfbfb02a346f25461ea1498aa 100644 (file)
--- 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
 ---------------------