From: Bruno Harbulot <Bruno.Harbulot@manchester.ac.uk>
To: git@vger.kernel.org
Subject: git-svn clone on a central server
Date: Sat, 15 Mar 2008 19:38:40 +0000 [thread overview]
Message-ID: <frh8k1$lc8$1@ger.gmane.org> (raw)
Hello,
I'm trying to follow example 3 of the git-svn manpage, since I'd like to
keep a "central" clone of a subversion repository (and rebase it
regularly) on a server and work on local git repositories based on that
server's git repository.
However, I can't get this example to work:
# Do the initial import on a server
ssh server "cd /pub && git-svn clone http://svn.foo.org/project
# 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
git-svn init http://svn.foo.org/project
# Pull the latest changes from Subversion
git-svn rebase
('--add' doesn't work in git config, but I guess that's not required).
I get this error:
$ git-svn rebase
fatal: ambiguous argument 'HEAD': unknown revision or path not in the
working tree.
Use '--' to separate paths from revisions
log --no-color HEAD: command returned error: 128
I've then tried:
$ git checkout origin/master
warning: You appear to be on a branch yet to be born.
[...]
$ git branch master
$ git checkout master
$ git-svn rebase
However, this produces this error:
'Unable to determine upstream SVN information from working tree history'
Any idea how to solve this?
Best wishes,
Bruno.
next reply other threads:[~2008-03-15 19:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-15 19:38 Bruno Harbulot [this message]
2008-03-15 23:45 ` git-svn clone on a central server Peter Harris
2008-03-16 14:47 ` Bruno Harbulot
2008-03-17 15:01 ` Peter Harris
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='frh8k1$lc8$1@ger.gmane.org' \
--to=bruno.harbulot@manchester.ac.uk \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox