All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pawel Sikora <pluto@agmk.net>
To: git@vger.kernel.org
Subject: why git-svn dcommit recreates master branch?
Date: Wed, 11 Jan 2012 17:27:05 +0100	[thread overview]
Message-ID: <2397908.s01vAlxMN3@pawels> (raw)

[-- Attachment #1: Type: text/plain, Size: 1218 bytes --]

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.

[-- Attachment #2: test.sh --]
[-- Type: application/x-shellscript, Size: 489 bytes --]

                 reply	other threads:[~2012-01-11 16:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2397908.s01vAlxMN3@pawels \
    --to=pluto@agmk.net \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.