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

Re: What's cooking in git.git (May 2015, #05; Tue, 19)

From
Jeff King <peff@peff.net>
Date
May 19, 2015, 22:28 UTC
Message-ID
<20150519222843.GB994@peff.net>
In-Reply-To
<xmqqbnhg6y8h.fsf@gitster.dls.corp.google.com>
On Tue, May 19, 2015 at 02:42:06PM -0700, Junio C Hamano wrote:
Show 10 quoted lines
> * jk/http-backend-deadlock (2015-05-15) 2 commits
>  - http-backend: spool ref negotiation requests to buffer
>  - http-backend: fix die recursion with custom handler
> 
>  Communication between the HTTP server and http_backend process can
>  lead to a dead-lock when relaying a large ref negotiation request.
>  Diagnose the situation better, and mitigate it by reading such a
>  request first into core (to a reasonable limit).
> 
>  Will merge to 'next'.

FYI, my plan was to re-roll this with a configurable max-buffer value (and a higher default). That can come on top if you prefer, though.

-Peff
Previous: Junio C HamanoNext: Junio C Hamano
Message 2 of 3 in “What's cooking in git.git (May 2015, #05; Tue, 19)”
  1. Junio C HamanoMay 19, 2015
  2. Jeff KingMay 19, 2015
  3. Junio C HamanoMay 19, 2015

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.