diff options
author | Junio C Hamano <junio@hera.kernel.org> | 2007-08-07 06:06:11 +0000 |
---|---|---|
committer | Junio C Hamano <junio@hera.kernel.org> | 2007-08-07 06:06:11 +0000 |
commit | e9bfa9b2c97714ddb520595db729bcad416ce1d3 (patch) | |
tree | 2a930ee7d3670603fe42acbecf88f1ad3ae88be3 /git-svn.txt | |
parent | bd2b4bbb74c94d27ad61268c94f4cbde040b2fec (diff) | |
download | git-htmldocs-e9bfa9b2c97714ddb520595db729bcad416ce1d3.tar.gz |
Autogenerated HTML docs for v1.5.3-rc4-24-g5b56a
Diffstat (limited to 'git-svn.txt')
-rw-r--r-- | git-svn.txt | 20 |
1 files changed, 20 insertions, 0 deletions
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 --------------------- |