From: Alejandro Colomar <alx.manpages@gmail.com>
To: linux-man <linux-man@vger.kernel.org>
Subject: Re: STANDARDS, VERSIONS, HISTORY
Date: Fri, 31 Mar 2023 21:46:05 +0200 [thread overview]
Message-ID: <d1300513-bd48-7971-0169-97b4c0f7e7c5@gmail.com> (raw)
In-Reply-To: <c2947f22-a50c-96ef-e61c-6676968c9346@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1327 bytes --]
On 3/31/23 21:44, Alejandro Colomar wrote:
> Hi!
>
> I rewrote these sections. That's the reason I'm being slowish in
> replying to email, and now I'll be checking old mail for some time, so
> I may still take some time to review some mails. Sorry; I hope you
> find it worthy :)
>
> Please comment on this recent patch (currently the commit at HEAD) if
> there's anything you'd like to improve. It's a huge one, so reviewing
> it would be crazy, but feel free to comment on anything you don't like
> about these sections now that I changed them.
>
> TL;DR:
>
> STANDARDS now almost only covers C11 and POSIX.1-2008. Everything
> older goes to HISTORY. Soon (as soon as the new standards are
> published, so one year or so), STANDARDS will only cover C23 and
> POSIX.1-202x (2023?), and C11 and POSIX.1-2008 will be moved to
> HISTORY.
Also, the wording in these sections has been made consistent, and in
most cases, there's even no wording, but rather a list of standards or
systems in which an API is defined.
>
> VERSIONS mostly covers variants of an API in different systems, or
> different APIs that provide the same functionality (less often).
>
> Cheers,
> Alex
>
--
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-03-31 19:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 19:44 STANDARDS, VERSIONS, HISTORY Alejandro Colomar
2023-03-31 19:46 ` 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=d1300513-bd48-7971-0169-97b4c0f7e7c5@gmail.com \
--to=alx.manpages@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