git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: How to get rid of doubled branch after renaming a branch in svn-repository

From
Ppacco@tropezien.de <pacco@tropezien.de>
Date
Dec 1, 2010, 15:08 UTC
Message-ID
<35e60ee2f6d83801d130d53a56a8ae18@tropezien.de>
In-Reply-To
<4CF6553C.70500@drmicha.warpmail.net>
 Hi Michael,
 On Wed, 01 Dec 2010 15:01:32 +0100, Michael J Gruber 
 <git@drmicha.warpmail.net> wrote:
 [snipped]
Show 11 quoted lines
> svn records the rename as a copy+delete (it also sets some rename 
> info
> which git-svn seems to ignore). So, git-svn stays on the safe side by
> keeping the branch. Note that deleting the branch would possibly 
> delete
> at least some info since the branch name is not recorded in the 
> commit
> (if you use svn.noMetadata).
>
> You can safely delete the branch if you're sure its head commit is
> contained in some other branch (as will be for an ordinary rename).
 thank you for your explanation. I suspected that this issue might be a 
 mixture of different VCS-philosophy and uncertainty-handling.
 Okay, then I will delete the branch manually. Of course I would have 
 preferred to have an automatic solution, because I got attention on this 
 renaming by accident. I hope renaming a branch will not become a new 
 trend in repository actions.
 pacco
Previous: Michael J Gruber
Message 3 of 3 in “How to get rid of doubled branch after renaming a branch in svn-repository”
  1. pacco@tropezien.deDec 1, 2010
  2. Michael J GruberDec 1, 2010
  3. pacco@tropezien.deDec 1, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.