From: Ulrich Drepper <drepper@redhat.com>
To: Roland McGrath <roland@redhat.com>
Cc: GNU libc hackers <libc-hacker@sources.redhat.com>
Subject: Re: separately compiling libc modules for rtld
Date: Tue, 01 Oct 2002 00:31:00 -0000 [thread overview]
Message-ID: <3D994F6A.8060709@redhat.com> (raw)
In-Reply-To: <200210010645.g916jJ510346@magilla.sf.frob.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Roland McGrath wrote:
> But it is some untested new subtlety, so if 2.3 is very imminent
> I don't know if this should wait for 2.3.1.
I'd rather prefer to wait for 2.3.1. This looks like a patch which can
have many hidden possibilites to break something.
I know that Hurd has problems. But exported symbols temporarily should
be able to fix that, right? And it also doesn't introduce any permanent
ABI damage. So I'd rather go this way unless you prefer to not change
the code and declare 2.3.1 as the first release usable for Hurd.
- --
- --------------. ,-. 444 Castro Street
Ulrich Drepper \ ,-----------------' \ Mountain View, CA 94041 USA
Red Hat `--' drepper at redhat.com `---------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQE9mU9q2ijCOnn/RHQRAupgAJ9BdeHtvdC3mCPI6Xcp49cEkrVMdACfSo23
g4xVDujA+Qv09trt2QdAaEc=
=46PA
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2002-10-01 7:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-30 23:45 Roland McGrath
2002-10-01 0:31 ` Ulrich Drepper [this message]
2002-10-01 1:25 ` Roland McGrath
2002-10-01 1:26 ` Jakub Jelinek
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=3D994F6A.8060709@redhat.com \
--to=drepper@redhat.com \
--cc=libc-hacker@sources.redhat.com \
--cc=roland@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).