From: David Turner <David.Turner@twosigma.com>
To: Shawn Pearce <spearce@spearce.org>
Cc: git <git@vger.kernel.org>
Subject: RE: [PATCH] http.postbuffer: make a size_t
Date: Thu, 30 Mar 2017 20:59:31 +0000 [thread overview]
Message-ID: <82ec49a3ae4d402daf6113cf19c47fb0@exmbdft7.ad.twosigma.com> (raw)
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.
next prev parent reply other threads:[~2017-03-30 20:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-30 20:29 [PATCH] http.postbuffer: make a size_t David Turner
2017-03-30 20:42 ` Shawn Pearce
2017-03-30 20:59 ` David Turner [this message]
2017-03-30 22:07 ` Junio C Hamano
2017-03-31 4:22 ` Torsten Bögershausen
2017-03-31 15:52 ` David Turner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=82ec49a3ae4d402daf6113cf19c47fb0@exmbdft7.ad.twosigma.com \
--to=david.turner@twosigma.com \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.