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

Re: [PATCH] upload-pack: keep poll(2)'s timeout to -1

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 22, 2014, 18:26 UTC
Message-ID
<xmqqsikonzx0.fsf@gitster.dls.corp.google.com>
In-Reply-To
<20140822162711.GA8598@debian>
Edward Thomson <ethomson@edwardthomson.com> writes:
Show 9 quoted lines
> On Fri, Aug 22, 2014 at 12:03:34PM -0400, Jeff King wrote:
>> 
>> Yeah, I wasn't thinking we would get negative values from the user (we
>> don't document them at all), but we should probably do something
>> sensible. Let's just leave it at Ed's patch.
>
> Thanks, both.  Apologies for the dumb question: is there anything
> additional that I need to do (repost with your Acked-by, for example)
> or is this adequate as-is?
I've picked it up and queued it on 'pu'.  Thanks.
commit 6c71f8b0d3d39beffe050f92f33a25dc30dffca3
Author: Edward Thomson <ethomson@edwardthomson.com>
Date:   Fri Aug 22 15:19:11 2014 +0000
    upload-pack: keep poll(2)'s timeout to -1
    
    Keep poll's timeout at -1 when uploadpack.keepalive = 0, instead of
    setting it to -1000, since some pedantic old systems (eg HP-UX) and
    the gnulib compat/poll will treat only -1 as the valid value for
    an infinite timeout.
    
    Signed-off-by: Edward Thomson <ethomson@microsoft.com>
    Acked-by: Jeff King <peff@peff.net>
    Signed-off-by: Junio C Hamano <gitster@pobox.com>
Previous: Edward ThomsonNext: Junio C Hamano
Message 6 of 8 in “upload-pack: keep poll(2)'s timeout to -1”
  1. upload-pack: keep poll(2)'s timeout to -1Edward Thomson, Aug 22, 2014
  2. Jeff KingAug 22, 2014
  3. Junio C HamanoAug 22, 2014
  4. Jeff KingAug 22, 2014
  5. Edward ThomsonAug 22, 2014
  6. Junio C HamanoAug 22, 2014
  7. Junio C HamanoAug 22, 2014
  8. Junio C HamanoAug 22, 2014

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.