public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox•com>
To: Karsten Blees <karsten.blees@gmail•com>
Cc: "Keller\, Jacob E" <jacob.e.keller@intel•com>,
	"j6t\@kdbg.org" <j6t@kdbg•org>,
	"git\@vger.kernel.org" <git@vger•kernel.org>,
	"sortie\@maxsi.org" <sortie@maxsi•org>
Subject: Re: [PATCH 8/9] autoconf: Check for timer_settime
Date: Wed, 10 Sep 2014 14:08:28 -0700	[thread overview]
Message-ID: <xmqq38bzgp4j.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <54106F34.90505@gmail.com> (Karsten Blees's message of "Wed, 10 Sep 2014 17:33:08 +0200")

Karsten Blees <karsten.blees@gmail•com> writes:

> While the timer extension (timer_settime) has graduated to mandatory in
> the current POSIX spec, the monotonic clock extension is still optional
> today (i.e. not necessarily supported even on newer Unices). In contrast
> to this, the XSI extensions seem to be widely supported.
>
> IMO the 'obsolescent' marker in the current POSIX spec is no reason to
> spring into action (at least not yet). E.g. utimes (also in <sys/time.h>)
> has been marked LEGACY in the 2004 version and is no longer LEGACY today.
> Btw., we'd also have to find a replacement for gettimeofday and probably
> a lot of other stuff...
>
> Therefore I tend to agree with Hannes that we should stick with setitimer
> and emulate it on systems that don't have it (as we do on Windows).

Sounds sensible to me.

  reply	other threads:[~2014-09-10 21:08 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-29 16:42 [PATCH 1/9] git-compat-util.h: Add missing semicolon after struct itimerval Jacob Keller
2014-08-29 16:42 ` [PATCH 2/9] autoconf: Check for " Jacob Keller
2014-08-29 16:42 ` [PATCH 3/9] autoconf: Check for setitimer Jacob Keller
2014-08-29 16:42 ` [PATCH 4/9] autoconf: Check for timer_t Jacob Keller
2014-08-29 18:20   ` Jonas 'Sortie' Termansen
2014-08-29 16:42 ` [PATCH 5/9] autoconf: Check for struct timespec Jacob Keller
2014-08-29 16:42 ` [PATCH 6/9] autoconf: Check for struct sigevent Jacob Keller
2014-08-29 16:42 ` [PATCH 7/9] autoconf: Check for struct itimerspec Jacob Keller
2014-08-29 16:42 ` [PATCH 8/9] autoconf: Check for timer_settime Jacob Keller
2014-08-29 17:26   ` Johannes Sixt
2014-08-29 17:40     ` Keller, Jacob E
2014-09-10 15:33       ` Karsten Blees
2014-09-10 21:08         ` Junio C Hamano [this message]
2014-09-10 21:13           ` Keller, Jacob E
2014-08-29 16:42 ` [PATCH 9/9] Use timer_settime for new platforms Jacob Keller
2014-08-29 18:02   ` Junio C Hamano
2014-08-29 18:09     ` Keller, Jacob E
2014-08-29 18:12   ` Junio C Hamano
2014-08-29 16:48 ` [PATCH 1/9] git-compat-util.h: Add missing semicolon after struct itimerval Keller, Jacob E
2014-08-29 18:54   ` Jonas 'Sortie' Termansen
2014-08-29 19:07     ` Junio C Hamano
2014-08-29 19:43       ` Jonas 'Sortie' Termansen
2014-09-03  0:17         ` Keller, Jacob E
  -- strict thread matches above, loose matches on Subject: below --
2014-08-28  1:04 [PATCH 0/9] Use timer_settime for new platforms Jonas 'Sortie' Termansen
2014-08-28  1:04 ` [PATCH 8/9] autoconf: Check for timer_settime Jonas 'Sortie' Termansen
2014-08-29 15:23   ` Keller, Jacob E
2014-08-29 16:02     ` Jonas 'Sortie' Termansen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqq38bzgp4j.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    --cc=j6t@kdbg$(echo .)org \
    --cc=jacob.e.keller@intel$(echo .)com \
    --cc=karsten.blees@gmail$(echo .)com \
    --cc=sortie@maxsi$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox