From: "Joseph S. Myers" <joseph@codesourcery.com>
To: David Miller <davem@davemloft.net>
Cc: <libc-ports@sourceware.org>, <libc-alpha@sourceware.org>
Subject: Re: Architectures status 2012-12-18
Date: Wed, 19 Dec 2012 14:52:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1212191449270.26156@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20121219.013930.546849725830051814.davem@davemloft.net>
On Wed, 19 Dec 2012, David Miller wrote:
> I have this in my TODO list, but for glibc-2.18. This is an
> optimization and there is no reason to target it for 2.17
The point of the list is not so much that things should be done for a
particular release (although I'd certainly like to see a release
eventually where all systems are up to date, including Hurd, HPPA and
AM33), as to provide something more recent than the list I sent to
libc-ports several months ago to link from the general todo / projects
list <http://sourceware.org/glibc/wiki/Development_Todo/Master>.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2012-12-19 14:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-18 20:34 Joseph S. Myers
2012-12-18 22:20 ` Andreas Schwab
2012-12-19 9:39 ` David Miller
2012-12-19 14:52 ` Joseph S. Myers [this message]
2012-12-19 18:24 ` Carlos O'Donell
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=Pine.LNX.4.64.1212191449270.26156@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=davem@davemloft.net \
--cc=libc-alpha@sourceware.org \
--cc=libc-ports@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).