Hi Adam, Adam Borowski wrote:
> When running "git svn clone" on a large repository, every a few revisions > or a single big one it stops with: > > fatal: unable to run 'git-svn' > > git svn fetch resumes the clone, stopping again after a few revisions. If > you keep resuming it long enough, the clone ultimately succeeds. Hmm. That message means that git found a git-svn executable but failed to run it for some reason, for example because the fork() system call failed. Just a hunch, but: what is the state of your vm.overcommit_memory setting (/proc/sys/vm/overcommit_memory)? Starting with v1.6.5, git reports which system call actually failed, so output from that version or later would be helpful, too. Thanks, Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
