Skip to content

Commit

Permalink
git-svn(1): update instructions for resuming a git-svn clone
Browse files Browse the repository at this point in the history
git-svn expects its references under refs/remotes/*; but these will
not be copied or set by "git clone"; put in this man page the manual
fiddling that is required with current git-svn to get this to work.

Signed-off-by: Sam Vilain <sam.vilain@catalyst.net.nz>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
  • Loading branch information
Sam Vilain authored and Junio C Hamano committed Jan 26, 2008
1 parent 3cf3237 commit 2b0d103
Showing 1 changed file with 7 additions and 4 deletions.
11 changes: 7 additions & 4 deletions Documentation/git-svn.txt
Original file line number Diff line number Diff line change
Expand Up @@ -456,10 +456,13 @@ 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
# Clone locally - make sure the refs/remotes/ space matches the server
mkdir project
cd project
git-init
git remote add origin server:/pub/project
git config --add remote.origin.fetch=+refs/remotes/*:refs/remotes/*
git fetch
# 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
Expand Down

0 comments on commit 2b0d103

Please sign in to comment.