From: Leah Neukirchen <leah@vuxu.org>
To: "'Quentin Rameau' via voidlinux" <voidlinux@googlegroups.com>
Cc: Quentin Rameau <quinq@fifth.space>
Subject: Re: [PATCH] musl: move NPROCESSORS* constants to regular namespace
Date: Mon, 07 Nov 2022 15:28:32 +0100 [thread overview]
Message-ID: <87k046x2i7.fsf@vuxu.org> (raw)
In-Reply-To: <20221106190558.26434-1-quinq@fifth.space> (via voidlinux's message of "Sun, 6 Nov 2022 20:05:57 +0100")
"'Quentin Rameau' via voidlinux" <voidlinux@googlegroups.com> writes:
> Hi Leah,
>
> Thank you for taking the time to review this.
>
>> That will break current scripts using `getconf _NPROCESSORS_CONF`.
>> From the man page, it's not clear to me if things there need
>> underscores or not, but imo we should extend the script in a
>> backward-compatible way.
>
> I highly doubt anybody is relying on the constants from the reserved
> namespace, as on most other systems, those are exposed directly.
It also works on glibc, and a few packages use it:
http://codesearch.debian.net/search?q=getconf+_NPROCESSORS_CONF&literal=1
--
Leah Neukirchen <leah@vuxu.org> https://leahneukirchen.org/
--
You received this message because you are subscribed to the Google Groups "voidlinux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to voidlinux+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/voidlinux/87k046x2i7.fsf%40vuxu.org.
prev parent reply other threads:[~2022-11-07 14:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-06 8:09 'Quentin Rameau' via voidlinux
2022-11-06 18:07 ` Leah Neukirchen
2022-11-06 19:05 ` 'Quentin Rameau' via voidlinux
2022-11-06 19:05 ` [PATCH] musl: add " 'Quentin Rameau' via voidlinux
2022-11-07 14:28 ` Leah Neukirchen [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=87k046x2i7.fsf@vuxu.org \
--to=leah@vuxu.org \
--cc=quinq@fifth.space \
--cc=voidlinux@googlegroups.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 NNTP newsgroup(s).