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

Re: [PATCH v3] http.postbuffer: allow full range of ssize_t values

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 1, 2017, 18:09 UTC
Message-ID
<xmqqo9wguhhn.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<20170401060116.b2v7tyoi7fcxwbvo@sigill.intra.peff.net>
Jeff King <peff@peff.net> writes:
Show 11 quoted lines
> On Fri, Mar 31, 2017 at 01:26:31PM -0400, David Turner 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 still not sure why a 2GB post-buffer is necessary. It sounds like
> something is broken in your setup. Large pushes should be sent chunked.
>
> I know broken setups are a fact of life, but this feels like a really
> hacky work-around.

Yeah, I tend to share that "Huh? We do not want to do this, but what forces us to?" puzzlement.

Tentatively demoted to 'pu' (out of 'jch'--candidates to go to 'next').
Previous: Jeff KingNext: David Turner
Message 4 of 10 in “http.postbuffer: allow full range of ssize_t values”
  1. http.postbuffer: allow full range of ssize_t valuesDavid Turner, Mar 31, 2017
  2. Junio C HamanoMar 31, 2017
  3. Jeff KingApr 1, 2017
  4. Junio C HamanoApr 1, 2017
  5. David TurnerApr 3, 2017
  6. Jeff KingApr 4, 2017
  7. David TurnerApr 4, 2017
  8. Jeff KingApr 4, 2017
  9. Christian CouderApr 6, 2017
  10. Jeff KingApr 7, 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.