Subject: why git-svn dcommit recreates master branch?

From: Pawel Sikora <[email-masked]>
Date: Wed, 11 Jan 2012 17:27:05 +0100

Hi,

i'm wondering why the git-svn-dcommit recreates a master branch in my repo.
is it a bug or feature and master is required to cooperate with subversion?
please look at attached test.sh:

$ ./test.sh

Checked out revision 0.

A         file.txt
Adding         file.txt
Transmitting file data .
Committed revision 1.

Initialized empty Git repository in /home/users/pawels/bugs/git-svn-master-issue/repo.git/.git/
        A       file.txt
r1 = 464dbae76d675c8c4bdc715e34ebe46691b8bfa2 (refs/remotes/git-svn)
Checked out HEAD:
  file:///home/users/pawels/bugs/git-svn-master-issue/repo.svn r1

branches before dcommit:
* bridge
  remotes/git-svn

[bridge ffffc26] bar
 1 files changed, 1 insertions(+), 0 deletions(-)
Committing to file:///home/users/pawels/bugs/git-svn-master-issue/repo.svn ...
        M       file.txt
Committed r2
        M       file.txt
r2 = d98723bccdcf673790b55d47a4f345c694a68ced (refs/remotes/git-svn)
No changes between current HEAD and refs/remotes/git-svn
Resetting to the latest refs/remotes/git-svn

branches after dcommit:
* bridge
  master
  remotes/git-svn

could some one put some light on this?

BR,
Paweł.

please CC me on reply.