From: <pacco@tropezien.de>
To: <git@vger.kernel.org>
Subject: How to get rid of doubled branch after renaming a branch in svn-repository
Date: Wed, 01 Dec 2010 13:48:09 +0100 [thread overview]
Message-ID: <0a6b49e3cc0b08a717c0d6141073f32d@tropezien.de> (raw)
Hi,
I'm using git-svn as a tracking-tool for a Subversion repository.
I currently detected an unexpected branch, seeming dead, but visible
using 'git branch -a'. I checked the svn log and saw that someone has
moved/renamed a branch. That results in a deletion of the old branch and
an adding of a copy of the old branch with the new branch name.
The scenario is like that:
$ git branch -a
* master
remotes/svnrepos/git-svn-test
# Rename the branch (move) in the SVN-repos
$ svn mv https://svn.repos/branches/git-svn-test
https://svn.repos/branches/git-svn-test-new
# Update git-repository
$ git svn fetch
$ git branch -a
* master
remotes/svnrepos/git-svn-test
remotes/svnrepos/git-svn-test-new
You see the problem. Within Subversion simply a new repository version
now no longer "showing" the git-svn-test-branch was created. But within
git both branches stay visible.
Well, I know that renaming a branch is really not that favoured action.
But I expected that git-svn gathers also this deletion and removes the
obsolete branch.
So, am I doing something wrong? Or am I expecting the wrong behaviour?
Or is that simply a feature, not a bug, and must be handled manually?
next reply other threads:[~2010-12-01 12:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-01 12:48 pacco [this message]
2010-12-01 14:01 ` How to get rid of doubled branch after renaming a branch in svn-repository Michael J Gruber
2010-12-01 15:08 ` pacco
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=0a6b49e3cc0b08a717c0d6141073f32d@tropezien.de \
--to=pacco@tropezien.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).