From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: linux-man@vger.kernel.org
Subject: the correct way to say "POSIX 2024"
Date: Sat, 17 May 2025 16:43:56 -0500 [thread overview]
Message-ID: <20250517214356.cpueutlfgi6t2enl@illithid> (raw)
In-Reply-To: <dfcy75vkqhlitfddrvbtaufcir3mour2g6cczxstpp32fhkedn@wj7k34u2rk6l>
[-- Attachment #1: Type: text/plain, Size: 729 bytes --]
Hi Alex,
At 2025-05-17T23:16:20+0200, Alejandro Colomar wrote:
> On Sat, May 17, 2025 at 01:53:02PM -0700, Collin Funk wrote:
> > +"P2024" indicates that the signal was added or its definition changed in
> > +POSIX 2024.
>
> This should be "POSIX.1-2024", not "POSIX 2024".
Do you have a supporting reference for this? I thought that since the
POSIX standard was no longer organized into subdivisions in the way it
was historically (with POSIX.1, POSIX.2, POSIX.4a, and so on), that
"POSIX.1-2004" was something of a misnomer.
I checked <https://www.opengroup.org/austin/>, but that page seems
careful not to use _either_ formulation! (It instead refers only to
IEEE Std 1003.1-2024.)
Regards,
Branden
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-05-17 21:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-17 20:53 [PATCH 1/3] man/man7/signal.7: Mention SIGWINCH was standardized in POSIX-1.2024 Collin Funk
2025-05-17 20:53 ` [PATCH 2/3] man/man3/getenv.3: Mention secure_getenv " Collin Funk
2025-05-17 21:17 ` Alejandro Colomar
2025-05-17 21:25 ` Collin Funk
2025-05-17 21:34 ` Alejandro Colomar
2025-05-17 22:19 ` Collin Funk
2025-05-18 7:58 ` Alejandro Colomar
2025-05-23 3:18 ` Collin Funk
2025-05-23 10:07 ` Alejandro Colomar
2025-05-23 21:22 ` Collin Funk
2025-05-24 17:46 ` Alejandro Colomar
2025-05-17 20:53 ` [PATCH 3/3] man/man3/ptsname.3: Mention ptsname_r " Collin Funk
2025-05-17 21:20 ` Alejandro Colomar
2025-05-17 21:16 ` [PATCH 1/3] man/man7/signal.7: Mention SIGWINCH " Alejandro Colomar
2025-05-17 21:43 ` G. Branden Robinson [this message]
2025-05-17 22:40 ` the correct way to say "POSIX 2024" Mark Harris
2025-05-17 22:45 ` G. Branden Robinson
2025-05-18 7:12 ` Alejandro Colomar
2025-05-18 7:52 ` Alejandro Colomar
2025-05-17 22:10 ` [PATCH v2 1/2] man/man7/signal.7: Mention SIGWINCH was standardized in POSIX-1.2024 Collin Funk
2025-05-17 22:10 ` [PATCH v2 2/2] man/man3/getenv.3: Mention secure_getenv " Collin Funk
2025-05-18 8:02 ` Alejandro Colomar
2025-05-18 8:00 ` [PATCH v2 1/2] man/man7/signal.7: Mention SIGWINCH " Alejandro Colomar
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=20250517214356.cpueutlfgi6t2enl@illithid \
--to=g.branden.robinson@gmail.com \
--cc=linux-man@vger.kernel.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