From: Alejandro Colomar <alx@kernel.org>
To: linux-man@vger.kernel.org
Cc: Collin Funk <collin.funk1@gmail.com>, Seth McDonald <sethmcmail@pm.me>
Subject: Re: [PATCH v1] man/man7/standards.7: Document C27, C23, POSIX.1-2004, POSIX.1-2013, POSIX.1-2024, SUSv5
Date: Tue, 23 Dec 2025 14:53:23 +0100 [thread overview]
Message-ID: <aUqevQLaoR7Oq66D@devuan> (raw)
In-Reply-To: <4d36afef1c657d5f9ed4a0d121648b330d62ce2c.1766497736.git.alx@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 3123 bytes --]
On Tue, Dec 23, 2025 at 02:49:37PM +0100, Alejandro Colomar wrote:
> Cc: Collin Funk <collin.funk1@gmail.com>
> Reported-by: Seth McDonald <sethmcmail@pm.me>
> Signed-off-by: Alejandro Colomar <alx@kernel.org>
> ---
>
> Hi Seth,
>
> I've expanded standards(7) to include several standards that were
> undocumented. Thanks for the report!
>
>
> Have a lovely day!
> Alex
>
> man/man7/standards.7 | 27 +++++++++++++++++++++++++++
> 1 file changed, 27 insertions(+)
>
> diff --git a/man/man7/standards.7 b/man/man7/standards.7
> index a3ab6e219..1b685d213 100644
> --- a/man/man7/standards.7
> +++ b/man/man7/standards.7
> @@ -102,6 +102,14 @@ .SH DESCRIPTION
> This revision of the C language standard was ratified by ISO in 2011
> .RI ( "ISO/IEC 9899:2011" ).
> .TP
> +.B C17
> +This revision of the C language standard was ratified by ISO in 2018
> +.RI ( "ISO/IEC 9899:2018" ).
> +.TP
> +.B C23
> +This revision of the C language standard was ratified by ISO in 2024
> +.RI ( "ISO/IEC 9899:2024" ).
> +.TP
> .B LFS
> The Large File Summit specification, completed in 1996.
> This specification defined mechanisms that allowed 32-bit systems
> @@ -235,6 +243,10 @@ .SH DESCRIPTION
> TC1 in 2003
> and TC2 in 2004.
> .TP
> +.B POSIX.1-2004
> +This revision of POSIX is technically identical to POSIX.1-2001 with
> +Technical Corrigenda 1 and 2 applied.
> +.TP
> .B POSIX.1-2008
> .TQ
> .B SUSv4
> @@ -279,6 +291,10 @@ .SH DESCRIPTION
> .UR http://www.opengroup.org\:/austin/
> .UE .
> .TP
> +.B POSIX.1-2013
> +This revision of POSIX is technically identical to POSIX.1-2008 with
> +Technical Corrigendum 1 applied.
> +.TP
> .B SUSv4 2016 edition
> This is equivalent to POSIX.1-2008, with the addition of
> Technical Corrigenda 1 and 2 and the XCurses specification.
> @@ -295,6 +311,17 @@ .SH DESCRIPTION
> manual pages under sections 0p (header files), 1p (commands),
> and 3p (functions);
> thus one can write "man 3p open".
> +.TP
> +.B POSIX.1-2024
> +.TQ
> +.B SUSv5
> +Work on the next revision of POSIX.1/SUS
> +was completed and ratified in 2024.
> +.IP
> +Further information can be found on the
> +.UR http://www.opengroup.org/\:austin/
> +Austin Group web site
> +.UE .
Amended with
diff --git a/man/man7/standards.7 b/man/man7/standards.7
index 1b685d213..e9e4101b8 100644
--- a/man/man7/standards.7
+++ b/man/man7/standards.7
@@ -318,6 +318,10 @@ .SH DESCRIPTION
Work on the next revision of POSIX.1/SUS
was completed and ratified in 2024.
.IP
+POSIX.1-2024 is aligned with C17,
+so that all of the library functions standardized in C17
+are also standardized in POSIX.1-2024.
+.IP
Further information can be found on the
.UR http://www.opengroup.org/\:austin/
Austin Group web site
> .SH SEE ALSO
> .BR getconf (1),
> .BR confstr (3),
>
> Range-diff against v0:
> -: --------- > 1: 4d36afef1 man/man7/standards.7: Document C27, C23, POSIX.1-2004, POSIX.1-2013, POSIX.1-2024, SUSv5
> --
> 2.51.0
>
>
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2025-12-23 13:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-23 4:23 Outdated standards(7) page Seth McDonald
2025-12-23 12:44 ` Alejandro Colomar
2025-12-23 13:49 ` [PATCH v1] man/man7/standards.7: Document C27, C23, POSIX.1-2004, POSIX.1-2013, POSIX.1-2024, SUSv5 Alejandro Colomar
2025-12-23 13:53 ` Alejandro Colomar [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=aUqevQLaoR7Oq66D@devuan \
--to=alx@kernel.org \
--cc=collin.funk1@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=sethmcmail@pm.me \
/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