public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "clameter at sgi dot com" <sourceware-bugzilla@sources.redhat.com>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/220] IA64: return EINVAL if ITC is an unreliable time source on clock_gettime(CLOCK_PROCESS_TIMEID)
Date: Mon, 14 Jun 2004 22:25:00 -0000 [thread overview]
Message-ID: <20040614222536.28841.qmail@sourceware.org> (raw)
In-Reply-To: <20040614204748.220.clameter@sgi.com>
------- Additional Comments From clameter at sgi dot com 2004-06-14 22:25 -------
Subject: Re: IA64: return EINVAL if ITC is an unreliable time
source on clock_gettime(CLOCK_PROCESS_TIMEID)
I must somehow missed that options. I was looking for it. When I followed
your link I found the function to post an attachment.
On Mon, 14 Jun 2004, schwab at suse dot de wrote:
>
> ------- Additional Comments From schwab at suse dot de 2004-06-14 21:50 -------
> Still you should follow the GNU coding conventions, and put patches in
> attachments so that they can be retrieved unmangled.
>
> --
>
>
> http://sources.redhat.com/bugzilla/show_bug.cgi?id=220
>
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
>
--
http://sources.redhat.com/bugzilla/show_bug.cgi?id=220
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2004-06-14 22:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-14 20:47 [Bug libc/220] New: " clameter at sgi dot com
2004-06-14 20:50 ` [Bug libc/220] " clameter at sgi dot com
2004-06-14 21:50 ` schwab at suse dot de
2004-06-14 22:24 ` clameter at sgi dot com
2004-06-14 22:25 ` clameter at sgi dot com [this message]
2004-06-15 7:57 ` jakub at redhat dot com
2004-06-15 21:56 ` clameter at sgi dot com
2004-08-10 2:14 ` drepper at redhat dot com
2004-08-10 17:17 ` clameter at sgi dot com
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=20040614222536.28841.qmail@sourceware.org \
--to=sourceware-bugzilla@sources.redhat.com \
--cc=glibc-bugs@sources.redhat.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).