3

Possible Duplicate:
git-svn clone | spurious branches

I converted an SVN repo to git with git-svn.

Everything seems to be fine, but there a lot of branches named branch-name@rev (i.e. remotes/release-1.0@10920), which are not in SVN.

Does anybody know where they come from?

Community
  • 1
  • 1
lweller
  • 11,077
  • 3
  • 34
  • 38

2 Answers2

1

This may not be the only time those kinds of refs show up, but one place where they do show up is when the entire project was moved (renamed) in svn.

Tyler
  • 21,762
  • 11
  • 61
  • 90
  • Posted similar issue in http://stackoverflow.com/questions/11356901/git-svn-clone-spurious-branches. But the reported branches weren't deleted or moved. Even for some of the normal commit revisions, these branches are created. Any idea why this happens ? – crankparty Jul 13 '12 at 07:32
0

I have faced this problem too. Remember to use the -s option to tell git that your svn is of a particular standard layout and all should be good.

lprsd
  • 84,407
  • 47
  • 135
  • 168