From: David Turner <david.turner@twosigma.com>
Date: Thu, 30 Mar 2017 20:59:31 GMT
Subject: RE: [PATCH] http.postbuffer: make a size_t
Message-ID: <82ec49a3ae4d402daf6113cf19c47fb0@exmbdft7.ad.twosigma.com>
In-Reply-To: <CAJo=hJvs0UKO_NLbWAi8Y8XRJJ0v5kdjf9BN0V=pN_9yYrDp7Q@mail.gmail.com>

GitLab.  I can't speak to our particular configuration of it -- but if you have a specific question about what the config is, I can ask our gitlab admins.

> -----Original Message-----
> From: Shawn Pearce [mailto:spearce@spearce.org]
> Sent: Thursday, March 30, 2017 4:42 PM
> To: David Turner <David.Turner@twosigma.com>
> Cc: git <git@vger.kernel.org>
> Subject: Re: [PATCH] http.postbuffer: make a size_t
> 
> On Thu, Mar 30, 2017 at 1:29 PM, David Turner <dturner@twosigma.com>
> wrote:
> > Unfortunately, in order to push some large repos, the http postbuffer
> > must sometimes exceed two gigabytes.  On a 64-bit system, this is OK:
> > we just malloc a larger buffer.
> 
> I'm slightly curious what server you are pushing to that needs the entire thing
> buffered to compute a Content-Length, rather than using
> Transfer-Encoding: chunked. Most Git-over-HTTP should be accepting
> Transfer-Encoding: chunked when the stream exceeds postBuffer.