public inbox for libc-hacker@sourceware.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@redhat.com>
To: Ulrich Drepper <drepper@redhat.com>
Cc: libc-hacker@sourceware.org
Subject: Re: [PATCH] Don't call uname or getrlimit in libpthread init function
Date: Fri, 09 Apr 2010 08:18:00 -0000	[thread overview]
Message-ID: <m3bpdtm43i.fsf@hase.home> (raw)
In-Reply-To: <4BBE69D7.7030009@redhat.com> (Ulrich Drepper's message of "Thu, 08 Apr 2010 16:42:15 -0700")

Ulrich Drepper <drepper@redhat.com> writes:

> If you replace a function then do it right and everything will work
> correctly.

So what's wrong with
<http://sourceware.org/ml/libc-alpha/2010-04/msg00017.html>?

Andreas.

-- 
Andreas Schwab, schwab@redhat.com
GPG Key fingerprint = D4E8 DBE3 3813 BB5D FA84  5EC7 45C6 250E 6F00 984E
"And now for something completely different."

      reply	other threads:[~2010-04-09  8:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-08  9:43 Andreas Schwab
2010-04-08 22:36 ` Ulrich Drepper
     [not found]   ` <m2y6gxy1po.fsf@igel.home>
2010-04-08 23:42     ` Ulrich Drepper
2010-04-09  8:18       ` Andreas Schwab [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=m3bpdtm43i.fsf@hase.home \
    --to=schwab@redhat.com \
    --cc=drepper@redhat.com \
    --cc=libc-hacker@sourceware.org \
    /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).