From: Alastair Houghton <firstname.lastname@example.org>
To: email@example.com, Rich Felker <firstname.lastname@example.org>
Subject: Re: [musl] setlocale() again
Date: Mon, 18 Sep 2023 15:18:03 +0100 [thread overview]
Message-ID: <3DD8D02A-0802-494E-B9E8-F00B457B86F6@apple.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1378 bytes --]
Hi all (Rich especially though :-))
Has anyone had time to take a look at this? I’d like to make some progress on this front if possible.
> On 5 Sep 2023, at 13:57, Alastair Houghton <email@example.com> wrote:
> On 10 Aug 2023, at 16:51, Rich Felker <firstname.lastname@example.org> wrote:
>> On Thu, Aug 10, 2023 at 04:41:38PM +0100, Alastair Houghton wrote:
>>> I spent some time today looking at the setlocale() problem and
>>> thought I’d put some notes down in an email.
>> At this point, it's been quite a while since I looked at the
>> mechanisms. If you'd like to help move this forward, rather than
>> starting with a patch, writing a high-level natural language
>> description of how you'd make the changes (in terms of musl's current
>> internal representation for locale state) would be the most helpful.
>> If I'm forgetting and there's already such a good description, just
>> digging it up and citing it might be fine.
> I wrote something up here:
> Let me know what you think; I can update the document there until we’re happy that we’ve got the right solution, then I should be able to create a patch and get the relevant permission from my employer to submit it.
> Kind regards,
[-- Attachment #2: Type: text/html, Size: 8276 bytes --]
next prev parent reply other threads:[~2023-09-18 14:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-10 15:41 Alastair Houghton
2023-08-10 15:51 ` Rich Felker
2023-09-05 12:57 ` Alastair Houghton
2023-09-18 14:18 ` Alastair Houghton [this message]
2023-10-27 20:15 ` Pablo Correa Gomez
2023-11-28 16:27 ` Alastair Houghton
2023-11-28 23:15 ` Pablo Correa Gomez
2023-11-28 17:32 ` Alastair Houghton
2023-11-28 23:21 ` Pablo Correa Gomez
2023-12-05 15:19 ` Alastair Houghton
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).