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

git-svn: Out of memory while cloning large (cca. 48000 commits) SVN repo

From
GPGergely Polonkai <gergely@polonkai.eu>
Date
Apr 28, 2014, 21:26 UTC
Message-ID
<CACczBUL0N0D2rqwQ0p=that4ejN-aa-er_DTJvJVh-hax5mxmA@mail.gmail.com>
Hello,

I’m trying to clone an SVN repository with around 48000 revisions, several branches and tags (svn://svn.zabbix.com). After a few thousands commits, Git failed (complaining something about sed, I haven’t wrote that down), so I svnrdumped the whole repository onto my filesystem.

After that, I used this command:
git svn clone -s --prefix=origin/ file://`pwd`/zabbix-svn zabbix-git/

to dump all the repo into a new Git repository. It ran for around 24 hours to report an Out of memory error at the end. Although I realised since then that this was a somewhat bad idea, I still don’t think it should happen this way. Or should it?

Best, Gergely

Message 1 of 1 in “git-svn: Out of memory while cloning large (cca. 48000 commits) SVN repo”
  1. Gergely PolonkaiApr 28, 2014

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.