git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] http.postbuffer: make a size_t

From
Shawn Pearce <spearce@spearce.org>
Date
Mar 30, 2017, 20:42 UTC
Message-ID
<CAJo=hJvs0UKO_NLbWAi8Y8XRJJ0v5kdjf9BN0V=pN_9yYrDp7Q@mail.gmail.com>
In-Reply-To
<20170330202917.24281-1-dturner@twosigma.com>
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.
Previous: David TurnerNext: David Turner
Message 2 of 6 in “http.postbuffer: make a size_t”
  1. http.postbuffer: make a size_tDavid Turner, Mar 30, 2017
  2. Shawn PearceMar 30, 2017
  3. David TurnerMar 30, 2017
  4. Junio C HamanoMar 30, 2017
  5. Torsten BögershausenMar 31, 2017
  6. David TurnerMar 31, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.