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

Re: Git SVN Rebranching Issue

From
MKMatt Kern <matt.kern@undue.org>
Date
Nov 4, 2008, 11:24 UTC
Message-ID
<20081104112409.GA21758@deimos.cyantechnology.local>
In-Reply-To
<20081104094224.GC24100@dpotapov.dyndns.org>
Show 6 quoted lines
> > It was actually an intentional design decision on my part preserve
> > parents based on branch name.  We would eventually otherwise lose
> > history of the now-deleted branches, as reflogs can expire.
> 
> Would it not be better to save the old branch using "@SVN-NUMBER" as
> suffix? Thus, those do not need the old branch can easily delete it.
I would second this approach.

Our svn repository isn't particularly big or old, but if someone were to make a branch now, there is a fair chance it will have the same name as an old branch but have absolutely nothing to do with that old branch. The situation will only get worse as our svn repository grows and more branches are created/deleted.

Matt
-- 
Matt Kern
http://www.undue.org/
Previous: Sverre RabbelierNext: Eric Wong
Message 5 of 9 in “Git SVN Rebranching Issue”
  1. Matt KernNov 3, 2008
  2. Eric WongNov 4, 2008
  3. Dmitry PotapovNov 4, 2008
  4. Sverre RabbelierNov 4, 2008
  5. Matt KernNov 4, 2008
  6. Eric WongNov 5, 2008
  7. Avery PennarunNov 5, 2008
  8. Eric WongNov 6, 2008
  9. Avery PennarunNov 6, 2008

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.