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

RE: [PATCH v3] Support for setitimer() on platforms lacking it

From
Joachim Schmitz <jojo@schmitz-digital.de>
Date
Sep 7, 2012, 18:29 UTC
Message-ID
<004701cd8d26$a7710cd0$f6532670$@schmitz-digital.de>
In-Reply-To
<7va9x1zszj.fsf@alter.siamese.dyndns.org>
Show 25 quoted lines
> From: Junio C Hamano [mailto:gitster@pobox.com]
> Sent: Friday, September 07, 2012 6:41 PM
> To: Joachim Schmitz
> Cc: git@vger.kernel.org
> Subject: Re: [PATCH v3] Support for setitimer() on platforms lacking it
> 
> "Joachim Schmitz" <jojo@schmitz-digital.de> writes:
> 
> > HP NonStop (currently) doesn't have setitimer(). The previous attempt of an
> > emulation (reverted by this commit) was not a real substitute for a recurring
> > itimer (as here we also don't have SA_RESTART, so can't re-arm the timer).
> > As setitimer() is only used in cases of perceived latency and it doesn't affect
> > correctness, it now gets disabled entirely, if NO_SETITIMER is set.
> > HP NonStop does provide struct itimerval, but other platforms may not, so this
> > is taken care of in this commit too, by setting NO_STRUCT_ITIMERVAL.
> >
> > Signed-off-by: Joachim Schmitz <jojo@schmitz-digital.de>
> 
> The end-result looks simple and nice (thanks for NO_STRUCT_ITIMERVAL).
> 
> As we are not going to include the earlier failed attempt in our
> longer-term history (i.e. 'master', that never rewinds), however,
> I would prefer to see a replacement patch (as opposed to this one
> that incrementally updates the previous failed attempt).  I could
> squash this into the previous one myself though ;-)
Yes, please ;-)
Bye, Jojo
Previous: Junio C Hamano
Message 3 of 3 in “RE: [PATCH v3] Support for setitimer() on platforms lacking it”
  1. Joachim SchmitzSep 7, 2012
  2. Junio C HamanoSep 7, 2012
  3. Joachim SchmitzSep 7, 2012

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.