Re: importing history

Christof Krüger [off-list ref] writes:

Now that you already have cloned the empty repository you can just look at
the remote configuration in it:

 git config --list|grep remote

You should see something like the following:

remote.origin.url=user@example.com/path/to/repository.git
remote.origin.fetch=+refs/heads/*:refs/remotes/origin/*

Go to your from-svn repository and add the above configuration, then "git
push origin master".

Careful.  git svn uses the remotes namespace in a non-std way.  Better
to locally clone the from-svn repository into a new one, then use "git
remote add origin user@example.com/path/to/repository.git" to add the
remote repository.  Then you can safely push the master branch.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

On Mi, 2011-06-29 at 18:56 +0200, Andreas Schwab wrote:

Careful.  git svn uses the remotes namespace in a non-std way.  Better
to locally clone the from-svn repository into a new one, then use "git
remote add origin user@example.com/path/to/repository.git" to add the
remote repository.  Then you can safely push the master branch.

Doesn't git svn use svn-remove.svn.* and not remote.*?
I've been doing that before and it worked for me.

"git svn dcommit" and "git push" are orthogonal to my understanding. If
you have an example, where git svn doesn't play well with "usual" git
remotes, I'd be happy to see them.

Regards,
  Chris