From: Ulrich Drepper <drepper@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: [PATCH] Kill 4 warnings
Date: Wed, 10 Jul 2002 20:00:00 -0000 [thread overview]
Message-ID: <1026356492.24688.132.camel@myware.mynet> (raw)
In-Reply-To: <20020701134806.N20867@sunsite.ms.mff.cuni.cz>
[-- Attachment #1: Type: text/plain, Size: 551 bytes --]
On Mon, 2002-07-01 at 04:48, Jakub Jelinek wrote:
> Following patch fixes these warnings:
Thanks, I've applied it.
> BTW: Shouldn't the linuxthreads testcases use test skeleton too, so that
> if they hang (which is far more likely than in non-threaded tests) they
> will be killed after timeout?
Ideally, yes.
--
---------------. ,-. 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-07-11 3:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-01 4:48 Jakub Jelinek
2002-07-10 20:00 ` Ulrich Drepper [this message]
2003-07-11 15:07 Jakub Jelinek
2003-07-11 22:50 ` Ulrich Drepper
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=1026356492.24688.132.camel@myware.mynet \
--to=drepper@redhat.com \
--cc=jakub@redhat.com \
--cc=libc-hacker@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).