From: Roland McGrath <roland@redhat.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Ulrich Drepper <drepper@redhat.com>,
Glibc hackers <libc-hacker@sources.redhat.com>
Subject: Re: [PATCH] Fix [BZ #130, #131, #133]
Date: Thu, 29 Apr 2004 21:56:00 -0000 [thread overview]
Message-ID: <200404292156.i3TLuI9l029222@magilla.sf.frob.com> (raw)
In-Reply-To: Jakub Jelinek's message of Wednesday, 28 April 2004 19:59:46 +0200 <20040428175946.GO5191@sunsite.ms.mff.cuni.cz>
>
> * manual/resource.texi (sched_setaffinity, sched_getaffinity): Fix
> prototypes and description [BZ #131].
>
> * string/bits/string2.h (strpbrk): Cast NULL to char * [BZ #130].
> Patch by Ed Catmur <ed@catmur.co.uk>.
> * string/tst-inlcall.c (main): Add test for strpbrk.
> linuxthreads/
> * semaphore.c (sem_timedwait): Return -1 and set errno instead of
> returning error number [BZ #133]. Patch by <rmhaddad@yahoo.com>.
Applied.
Thanks,
Roland
prev parent reply other threads:[~2004-04-29 21:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-28 20:11 Jakub Jelinek
2004-04-29 21:56 ` Roland McGrath [this message]
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=200404292156.i3TLuI9l029222@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=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).