git-svn branches with revision id's in name

From: Stephen Duncan Jr <stephen.duncan@gmail.com>
Date: Jan 30, 2012, 19:42 UTC
Message-ID: <CAGYrzvwzrsZdHHnSBaMv-sD9mDGVQ-qFuks+JM6d-NQ9Wz9KwQ@mail.gmail.com>

A project I work on recently changed it's SVN structure, causing me to do a new git svn clone. The new structure is like this:

{project}/branches/
  /master
  /develop
  /qa
  /feature
    /feature1
    /feature2
  /release
    /release1
    /release2
  /hotfix
    /hotfix1
    /hotfix2

So I set up my svn-remote sections as follows:

[svn-remote "svn"]
  url = {url}
  fetch = {project}/branches/master:refs/remotes/trunk
  fetch = {project}/branches/develop:refs/remotes/develop
  fetch = {project}/branches/qa:refs/remotes/qa
  branches = {project}/branches/{feature,release,hotfix}/*:refs/remotes/*/*

This seems to have worked fine, for the most part, but unlike my previous git-svn checkouts, it has created several branches with revision numbers as part of the name:

$ git branch -a
* master
  remotes/develop
  remotes/develop@29271
  remotes/develop@32463
  remotes/develop@34103
  remotes/feature/xyz
  remotes/feature/xyz@26438
  remotes/feature/xyz@27542
  remotes/feature/xyz@35233

Why have these remote branches been created? What impact does this have on my checkout? Can I remove safely remove them? How? I was unable to figure out how to reference this behavior in order to search for information on it.

-- Stephen Duncan Jr www.stephenduncanjr.com