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

[PATCH] do not reset in_vain on non-novel acks

From
JTJonathan Tan <jonathantanmy@google.com>
Date
Sep 22, 2016, 18:36 UTC
Message-ID
<cover.1474568670.git.jonathantanmy@google.com>

This is regarding the packfile negotiation in fetch-pack. If there is a concern that MAX_IN_VAIN would be hit too early (as a consequence of the patch below), I'm currently investigating the possibility of improving the negotiation ability of the client side further (for example, by prioritizing refs or heads instead of merely prioritizing by date in the priority queue of objects), but I thought I'd send the patch out first anyway to see what others think.

Jonathan Tan (1):
  fetch-pack: do not reset in_vain on non-novel acks
 fetch-pack.c | 12 ++++++++++--
 1 file changed, 10 insertions(+), 2 deletions(-)
-- 
2.8.0.rc3.226.g39d4020
Next: Jonathan Tan
Message 1 of 6 in “do not reset in_vain on non-novel acks”
  1. do not reset in_vain on non-novel acksJonathan Tan, Sep 22, 2016
  2. fetch-pack: do not reset in_vain on non-novel acksJonathan Tan, Sep 22, 2016
  3. Junio C HamanoSep 22, 2016
  4. fetch-pack: do not reset in_vain on non-novel acksJonathan Tan, Sep 23, 2016
  5. Junio C HamanoSep 23, 2016
  6. Junio C HamanoSep 22, 2016

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.