# git svn can't handle giant commit

2 messages from 2011-12-19 to 2012-01-11. Participants: fREW Schmidt, Carlos Martín Nieto.
Thread: https://gitlist.dev/t/29208

## fREW Schmidt, 2011-12-19 15:28

Subject: git svn can't handle giant commit
Message-ID: <CADVrmKRySXFAAi5WgpgSrephbsY7JLBECF+c9ZX=_KnRxn3Lzg@mail.gmail.com>
URL: https://gitlist.dev/e/CADVrmKRySXFAAi5WgpgSrephbsY7JLBECF%2Bc9ZX%3D_KnRxn3Lzg%40mail.gmail.com

```
Hey guys,

I'm working on an import of some repos and I discovered that I can't
import a certain commit due to it's size.  This is the commit:

http://perlcritic.tigris.org/source/browse/perlcritic?view=rev&revision=2676

Clearly it's large :-)

Anyway, here's the error message I get:

   Svndiff data contains invalid instruction: Invalid diff stream:
[new] insn 4 overflows the new data section at
/opt/libexec/git-core/git-svn line 5653

This is not a deal breaker as I'm fairly sure I can do the clone in
pieces as opposed to from the root (I just did the root to get a list
of authors anyway) but it seems like there should be a way to handle
something like this...

--
fREW Schmidt
http://blog.afoolishmanifesto.com

```

## Carlos Martín Nieto, 2012-01-11 13:07

Subject: Re: git svn can't handle giant commit
Message-ID: <20120111130708.GB11984@beez.lab.cmartin.tk>
URL: https://gitlist.dev/e/20120111130708.GB11984%40beez.lab.cmartin.tk
In-Reply-To: <CADVrmKRySXFAAi5WgpgSrephbsY7JLBECF+c9ZX=_KnRxn3Lzg@mail.gmail.com>

```
On Mon, Dec 19, 2011 at 09:28:04AM -0600, fREW Schmidt wrote:
> Hey guys,
> 
> I'm working on an import of some repos and I discovered that I can't
> import a certain commit due to it's size.  This is the commit:
> 
> http://perlcritic.tigris.org/source/browse/perlcritic?view=rev&revision=2676
> 
> Clearly it's large :-)
> 
> Anyway, here's the error message I get:
> 
>    Svndiff data contains invalid instruction: Invalid diff stream:
> [new] insn 4 overflows the new data section at
> /opt/libexec/git-core/git-svn line 5653

What version of git are you using? I can't find any of those error
messages in the git repo, and it looks like it's the svn library that
is creating the error message.

   cmn

```
