From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: Revisiting byte-based C locale
Date: Thu, 4 Jun 2015 16:53:32 -0400 [thread overview]
Message-ID: <20150604205332.GS17573@brightrain.aerifal.cx> (raw)
In-Reply-To: <20150522022203.GA26651@brightrain.aerifal.cx>
On Thu, May 21, 2015 at 10:22:03PM -0400, Rich Felker wrote:
> Any new opinions on the topic? Or interest in re-emphasizing a
> previously stated opinion? :)
No new opinions on this? I've tentatively added drafting a new
proposed byte-based C locale patch as a roadmap item for this release
cycle, not necessarily to commit it, but as a way to re-evaluate
whether it's still costly to implement.
Rich
next prev parent reply other threads:[~2015-06-04 20:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 2:22 Rich Felker
2015-05-22 4:04 ` Josiah Worcester
2015-05-22 4:09 ` Rich Felker
2015-06-04 20:53 ` Rich Felker [this message]
2015-06-04 21:00 ` Christian Neukirchen
2015-06-05 1:39 ` Rich Felker
2015-06-05 4:48 ` Isaac Dunham
2015-06-05 8:58 ` Christian Neukirchen
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=20150604205332.GS17573@brightrain.aerifal.cx \
--to=dalias@libc.org \
--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).