From: Ulrich Drepper <drepper@redhat.com>
To: GNU libc hacker <libc-hacker@sources.redhat.com>
Subject: architecture status, please
Date: Wed, 19 Feb 2003 22:41:00 -0000 [thread overview]
Message-ID: <3E540803.3060703@redhat.com> (raw)
I think things have stablelized now and we can think about 2.3.2. Do
all architectures which worked in 2.3.1 work now? Are any other
architectures which didn't work in 2.3.1 close to working with the
current tree?
--
--------------. ,-. 444 Castro Street
Ulrich Drepper \ ,-----------------' \ Mountain View, CA 94041 USA
Red Hat `--' drepper at redhat.com `---------------------------
next reply other threads:[~2003-02-19 22:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-19 22:41 Ulrich Drepper [this message]
2003-02-19 23:03 ` Franz Sirl
2003-02-20 2:54 ` kaz Kojima
2003-02-20 4:51 ` [PATCH] SH: fix pread/pwrite (Was: architecture status, please) kaz Kojima
2003-02-20 5:32 ` Ulrich Drepper
2003-02-20 8:25 ` architecture status, please Andreas Jaeger
2003-02-25 14:15 ` Andreas Jaeger
2003-02-25 14:17 ` Jakub Jelinek
2003-02-20 19:35 ` Richard Henderson
2003-02-21 7:25 ` Richard Henderson
2003-02-20 21:12 ` Philip Blundell
2003-02-25 8:37 ` unwind info fix for ia64 David Mosberger
2003-02-27 9:33 ` Ulrich Drepper
2003-02-19 23:17 architecture status, please Steve Munroe
2003-02-19 23:35 ` Ulrich Drepper
2003-02-20 14:31 Martin Schwidefsky
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=3E540803.3060703@redhat.com \
--to=drepper@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).