public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "stefan dot puiu at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/1890] strerror() unnecessarily non thread-safe
Date: Wed, 23 Nov 2005 09:15:00 -0000 [thread overview]
Message-ID: <20051123091548.8413.qmail@sourceware.org> (raw)
In-Reply-To: <20051119151517.1890.stefan.puiu@gmail.com>
------- Additional Comments From stefan dot puiu at gmail dot com 2005-11-23 09:15 -------
Funny thing you insist keeping a broken design, breaking compatibility (check
out the autoconf wizardry required to be portable about strerror right now), all
that for some stupid "extra info", and still call *me* clueless.
Have a nice day.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=1890
------- 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:[~2005-11-23 9:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-19 15:15 [Bug libc/1890] New: " stefan dot puiu at gmail dot com
2005-11-22 18:13 ` [Bug libc/1890] " drepper at redhat dot com
2005-11-23 7:35 ` stefan dot puiu at gmail dot com
2005-11-23 8:31 ` drepper at redhat dot com
2005-11-23 9:15 ` stefan dot puiu at gmail dot com [this message]
2005-11-23 9:26 ` stefan dot puiu at gmail dot com
[not found] <bug-1890-131@http.sourceware.org/bugzilla/>
2020-12-21 2:43 ` jscott at posteo dot net
2023-06-15 9:48 ` fweimer at redhat dot com
2023-06-15 9:50 ` fweimer at redhat dot com
2023-10-26 23:20 ` gabravier at gmail dot com
2023-11-01 1:59 ` bruno at clisp dot org
2023-12-12 11:40 ` fweimer at redhat dot com
2023-12-12 12:21 ` bruno at clisp dot org
2023-12-13 9:39 ` fweimer at redhat 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=20051123091548.8413.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--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).