Can I specify a “chunk size” for git svn fetch?

Can I specify a “chunk size” for git svn fetch?

[Zak Whaley]

I asked this over on StackOverflow
(http://stackoverflow.com/q/5886993/665372) and someone suggested
asking this mailing list.

I'm cloning an SVN repo with git and everything seems to be working
fine. The very last revision I need to download contains a ~220MB zip
file.

I know this isn't an issue for git, however the school's server I'm
downloading it from hangs up half way through the file which
invalidates the entire index requiring that it re-download the
revision again.

Is there a way to tell git-svn fetch to get an index in multiple
chunks of a particular chunk-size or to retain the partial index if
the server hangs up?

Spec info:
Win7 with Cygwin 1.7.9-1
git & git-svn 1.7.4-1


Regards,

Zak Whaley

Re: Can I specify a “chunk size” for git svn fetch?

[Thomas Ferris Nicolaisen]

> Is there a way to tell git-svn fetch to get an index in multiple
> chunks of a particular chunk-size or to retain the partial index if
> the server hangs up?
>
> Spec info:
> Win7 with Cygwin 1.7.9-1
> git & git-svn 1.7.4-1
>

If you are willing to leave out the big zip file from your repository,
you could try the following:

Make two clones, one before the over-sized commit, and one for
afterwards.  Say the big commit was committed in revision 36, it would
be something like:

git svn clone -r1:35 url first-clone
git svn clone -r36:HEAD url second-clone

Now fetch the second repo into the first repo, and tie the history
together using _grafts_. I've made a screencast with an example of
grafting like this here:

http://blog.tfnico.com/2010/10/gitsvn-6-grafting-together-svn-history.html

(I'll cross-post this answer to StackOverflow as well).