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

How to migrate a complex directory structure from SVN to GIT?

From
AAsuka <c.bauers@gmx.de>
Date
Jan 17, 2012, 19:33 UTC
Message-ID
<1326828837924-7197567.post@n2.nabble.com>
Hi there,

I would like to migrate my svn repository to git. The structure looks like the following:

svn
   |_Project1
         |_subproject1
               |_branches
                      |_branch1
                      |_branch2
               |_trunk
               |_tags
                      |_tagv1
   |_Non-JavaProject
         |_subproject
   |_Project2
          |_AnotherSubproject
               |_SubSubproject
          |_Subproject2
               |_branches
               |_tags
          |_Subproject3
               |_trunk
          |_Subproject4
               |_Subsubproject
                       |_branches
                       |_tags
                       |_trunk

I would like to migrate all branches and tags .. but unfortunately sometimes I have just a trunk directory and no branches or tags directory. Sometimes the branches are in a subdirectory, sometimes in a subsubdirectory. So how can migrate my svn in an efficient way?

Thanks in advance Best wishes

-- View this message in context: http://git.661346.n2.nabble.com/How-to-migrate-a-complex-directory-structure-from-SVN-to-GIT-tp7197567p7197567.html Sent from the git mailing list archive at Nabble.com.

Next: Michael Haggerty
Message 1 of 4 in “How to migrate a complex directory structure from SVN to GIT?”
  1. AsukaJan 17, 2012
  2. Michael HaggertyJan 18, 2012
  3. Jehan BingJan 18, 2012
  4. David BarrJan 27, 2012

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.