From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: Re: Thinking ahead past 1.1.9 release, road to 1.2
Date: Mon, 20 Apr 2015 12:00:46 +0200 [thread overview]
Message-ID: <20150420100046.GQ2875@port70.net> (raw)
In-Reply-To: <20150420041740.GA24325@brightrain.aerifal.cx>
* Rich Felker <dalias@libc.org> [2015-04-20 00:17:41 -0400]:
> Beyond that, what's left to get us to a point that could be called
> musl 1.2?
>
> The only source-level items I have on the roadmap for musl itself
> right now (some of which might still get done in this release cycle)
> are the ABI-compat __*_chk functions and a bunch of i18n/m17n items:
>
> - Message translation for dynamic linker
> - LC_COLLATE support
> - IDN support for DNS lookups
> - Updating to latest Unicode
>
> Is there anything else that should be on this list that I'm missing?
>
arch/*/bits cleanup ?
more docs ?
prev parent reply other threads:[~2015-04-20 10:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-20 4:17 Rich Felker
2015-04-20 10:00 ` Szabolcs Nagy [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=20150420100046.GQ2875@port70.net \
--to=nsz@port70.net \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).