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

Re: git-svn question

From
Wesley J. Landaker <wjl@icecavern.net>
Date
Jul 15, 2010, 18:50 UTC
Message-ID
<201007151250.32974.wjl@icecavern.net>
In-Reply-To
<20100715171849.GA31823@heretic.net-ronin.org>
On Thursday, July 15, 2010 11:18:49 carbonated beverage wrote:
> I'm trying to figure out how to import a rather large SVN tree that has
> been around for a while, initially converted from CVS.
[...]
> Given multiple projects that are nested as such, is there a way to get
> git-svn to import the tree and be able to derive the tags and branches? 
> Also, this tree is a little over 1TiB in size, though a large chunk of
> that is due to the duplicates made by SVN's branches/tags.

That sounds pretty messed up. Someone may have better advice, but I'd probably approach it by doing one or more of the following:

  1) Fix it up with svndumpfilter first to get rid of useless or duplicated 
parts, then import it.
  2) Once imported into use git rebase and/or git filter-branch to clean 
things up until it's how you like it.
  3) If all else fails, archive the SVN repository (or the git imported 
equivalent), call it "old history", and then start over and manually import 
only the active and useful branches and tags into git.
Previous: carbonated beverage
Message 2 of 2 in “git-svn question”
  1. carbonated beverageJul 15, 2010
  2. Wesley J. LandakerJul 15, 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.