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

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

From
David Barr <davidbarr@google.com>
Date
Jan 27, 2012, 04:46 UTC
Message-ID
<CAFfmPPNQRtxXSiLRMSwf85t1spdX12zVEQQea0yORK5hN8b0oA@mail.gmail.com>
In-Reply-To
<4F1713D4.9000602@orb.com>
Show 9 quoted lines
> If however you have a more complex layout, you can use "git svn init", then
> edit .git/config to suit your needs, then run "git svn fetch".
> And by "suit your needs", I mean you can add multiple "fetch=..." lines.
> In my case, I ended up having one "fetch=..." for each trunk, branch and
> tag.
> It was not efficient, it took 2 weeks to convert <30k revisions, ~200
> branches/project, ~80 projects, but it works well enough for me.
>
>        Jehan

This is why we need to breath life into the git-remote-svn effort. We should be able to handle imports of that size in minutes. (Cost of dumping from SVN aside.)

-- David Barr

Previous: Jehan Bing
Message 4 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.