threads / discuss / 17177

git-svn clone -s fails to setup branches in git if the most recent svn commit was not to trunk

Subject: git-svn clone -s fails to setup branches in git if the most recent svn commit was not to trunk

## tl;dr

2 messages between Jan 14, 2009 and Jan 14, 2009.

replies: 1people: 2as markdown or json

Adam Soltys· Jan 14, 2009, 21:27 UTC · lore

I ran the following command to clone from an svn repository that followed the standard svn folder layout and had two branches:

svn clone -s svn://path/to/my_repo

I then typed:

git branch -r

Which returned:

origin/HEAD origin/master

I was expecting to see the branches and tags from the svn /branches and /tags folders but they did not appear.

I checked out origin/HEAD and origin/master to see what was there and I found they contained code from a subversion branch that was originally in the /branches folder. I noticed that this particular branch was the last place committed to in the svn repo. So I checked something into the /trunk of the svn repo, nuked the git repo, and ran the git svn clone command again. This time it worked as expected and "git branch -r" showed me all my tags and branches.

Boyd Stephen Smith Jr.· Jan 14, 2009, 22:04 UTC · re: Adam Soltys · lore

Re: git-svn clone -s fails to setup branches in git if the most recent svn commit was not to trunk

On Wednesday 2009 January 14 15:27:01 Adam Soltys wrote: <snip: git-svn weirdness when the last commit is to a branch/tag>

I already knew about this bug, but here is my "+1 please fix" mail.

-- 
Boyd Stephen Smith Jr.                     ,= ,-_-. =. 
bss@iguanasuicide.net                     ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy           `-'(. .)`-' 
http://iguanasuicide.net/                      \_/