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

git-svn: Why not use git-fast-import?

From
VLVictor Leschuk <vleschuk@accesssoftek.com>
Date
Sep 22, 2015, 09:12 UTC
Message-ID
<6AE1604EE3EC5F4296C096518C6B77EE5D0FDAB9D7@mail.accesssoftek.com>
Hello all, 
I've been playing with git-svn for some time already and as it seems to me there are two most important problems which make it hard to use in production for large repositories. Very low speed and large memory footprint of synchronization with SVN repos (I am talking about clone and fetch operations mostly). I was wondering why the git-fast-import is not used for these purposes? Are there any serious limitations which make it impossible?
I have found several alternative solutions which use git-fast-import but they all do only the initial import of a repo. I have looked through the documentation and didn't see why fast-import can't be used to sync an existing repo after the import. Am I missing something?
Thanks in advance for clarification.
Next: Jeff King
Message 1 of 2 in “git-svn: Why not use git-fast-import?”
  1. Victor LeschukSep 22, 2015
  2. Jeff KingSep 22, 2015

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.