From: Ulrich Drepper <drepper@redhat.com>
To: Roland McGrath <roland@frob.com>
Cc: GNU libc hackers <libc-hacker@sources.redhat.com>
Subject: Re: nanosleep in locarchive
Date: Tue, 14 May 2002 15:40:00 -0000 [thread overview]
Message-ID: <1021415821.2824.12.camel@myware.mynet> (raw)
In-Reply-To: <20020512221059.4861F1BA17@perdition.linnaean.org>
[-- Attachment #1: Type: text/plain, Size: 596 bytes --]
On Sun, 2002-05-12 at 15:10, Roland McGrath wrote:
> Any objection to this change? (On Hurd we have usleep but not nanosleep.
> This call doesn't need the finer granularity.)
This is true t I'd really like to avoid using any but the POSIX
interfaces. Are there any problems with implementing nanosleep for
Hurd? The precision does not have to be nanoseconds.
--
---------------. ,-. 1325 Chesapeake Terrace
Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
Red Hat `--' drepper at redhat.com `------------------------
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-05-14 22:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-12 15:11 Roland McGrath
2002-05-14 15:40 ` Ulrich Drepper [this message]
2002-05-14 18:08 ` Roland McGrath
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=1021415821.2824.12.camel@myware.mynet \
--to=drepper@redhat.com \
--cc=libc-hacker@sources.redhat.com \
--cc=roland@frob.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).