From: Alejandro Colomar <alx@kernel.org>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: Seth McDonald <sethmcmail@pm.me>, linux-man@vger.kernel.org
Subject: Re: [PATCH v1 01/12] man/man2const/F_DUPFD.2const: HISTORY: Update first POSIX appearance of F_DUPFD(2const)
Date: Mon, 5 Jan 2026 16:44:40 +0100 [thread overview]
Message-ID: <aVvbr9qBMV9Eohwh@devuan> (raw)
In-Reply-To: <20260105153227.6tm44wrjaonclphz@illithid>
[-- Attachment #1: Type: text/plain, Size: 1109 bytes --]
Hi Branden,
On Mon, Jan 05, 2026 at 09:32:27AM -0600, G. Branden Robinson wrote:
> At 2026-01-05T19:18:39+1000, Seth McDonald wrote:
> > F_GETFL(2const) and F_SETFL(2const) first appeared in POSIX.1-1988.[1]
> > -SVr4, 4.3BSD, POSIX.1-2001.
> > +SVr4,
> > +4.3BSD,
> > +POSIX.1-1988.
>
> What ordering is used for these?
Ideally, I would like it to be in chronologic order.
> 4.3BSD was 1986.[1]
>
> POSIX.1-1988 was, nominally, 1988 but we all know how standards
> sometimes lag. It seems the record is murky in this case.[2]
>
> I've seen dates of 1988 applied SVr4, but no reports that it was
> publicly available until 1989.[3]
If anyone wants to do research and improve those --as Seth is doing--,
I'll welcome patches. :)
Have a lovely New Year!
Alex
>
> Regards,
> Branden
>
> [1] https://www.oreilly.com/openbook/opensources/book/kirkmck.html
> [2] https://luplab.cs.ucdavis.edu/2021/11/04/the-hunt-for-posix-1-1988.html
> [3] http://ps-2.retropc.se/sites/unixarchive/Documentation/AUUGN/AUUGN-V09.6.pdf
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-01-05 15:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-05 9:18 [PATCH v1 00/12] man/man{2,3}const/*: Update POSIX history of constants Seth McDonald
2026-01-05 9:18 ` [PATCH v1 01/12] man/man2const/F_DUPFD.2const: HISTORY: Update first POSIX appearance of F_DUPFD(2const) Seth McDonald
2026-01-05 9:18 ` [PATCH v1 02/12] man/man2const/F_GETFD.2const: HISTORY: Update first POSIX appearance of F_[GS]ETFD(2const) Seth McDonald
2026-01-05 9:18 ` [PATCH v1 03/12] man/man2const/F_GETFL.2const: HISTORY: Update first POSIX appearance of F_[GS]ETFL(2const) Seth McDonald
2026-01-05 15:32 ` [PATCH v1 01/12] man/man2const/F_DUPFD.2const: HISTORY: Update first POSIX appearance of F_DUPFD(2const) G. Branden Robinson
2026-01-05 15:44 ` Alejandro Colomar [this message]
2026-01-05 9:18 ` [PATCH v1 04/12] man/man2const/IPPROTO_IP{V6,}.2const: HISTORY: Add sections Seth McDonald
2026-01-05 9:18 ` [PATCH v1 05/12] man/man2const/IPV6_MULTICAST_{HOPS,IF,LOOP}.2const: " Seth McDonald
2026-01-05 9:18 ` [PATCH v1 06/12] man/man2const/IPV6_UNICAST_HOPS.2const: HISTORY: Add section Seth McDonald
2026-01-05 9:18 ` [PATCH v1 07/12] man/man2const/IPV6_V6ONLY.2const: HISTORY: Add first POSIX appearance of IPV6_V6ONLY(2const) Seth McDonald
2026-01-05 9:18 ` [PATCH v1 08/12] man/man3const/EOF.3const: HISTORY: Update first POSIX appearance of EOF(3const) Seth McDonald
2026-01-05 9:18 ` [PATCH v1 09/12] man/man3const/EXIT_SUCCESS.3const: HISTORY: Split EXIT_SUCCESS(3const) and EXIT_FAILURE(3const) Seth McDonald
2026-01-05 9:18 ` [PATCH v1 10/12] man/man3const/EXIT_SUCCESS.3const: HISTORY: Update first POSIX appearance of EXIT_SUCCESS(3const) Seth McDonald
2026-01-05 9:18 ` [PATCH v1 11/12] man/man3const/EXIT_SUCCESS.3const: HISTORY: Update first POSIX appearance of EXIT_FAILURE(3const) Seth McDonald
2026-01-05 9:18 ` [PATCH v1 12/12] man/man3const/NULL.3const: HISTORY: Update first POSIX appearance of NULL(3const) Seth McDonald
2026-01-05 14:43 ` [PATCH v1 00/12] man/man{2,3}const/*: Update POSIX history of constants 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=aVvbr9qBMV9Eohwh@devuan \
--to=alx@kernel.org \
--cc=g.branden.robinson@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.