All of lore.kernel.org
 help / color / mirror / Atom feed
From: Collin Funk <collin.funk1@gmail.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: Seth McDonald <sethmcmail@pm.me>,
	 "linux-man@vger.kernel.org" <linux-man@vger.kernel.org>
Subject: Re: Early POSIX versions seldom included in history sections
Date: Sun, 21 Dec 2025 16:58:06 -0800	[thread overview]
Message-ID: <87bjjrbae9.fsf@gmail.com> (raw)
In-Reply-To: <aUfsE7Yt45BVO56T@devuan>

[-- Attachment #1: Type: text/plain, Size: 848 bytes --]

Hi Seth and Alex,

Alejandro Colomar <alx@kernel.org> writes:

>> Suppose instead a function was first introduced in SUSv2, included in
>> POSIX.1-2001 as an XSI extension, then in POSIX.1-2008 it was moved to
>> Base. Should its history section include POSIX.1-2001 or POSIX.1-2008 as
>> its first POSIX appearance (since XSI is SUS)?
>
> I think you could do this:
>
> SUSv2.
> POSIX.1-2001 (XSI).
> POSIX.1-2008.

Just want to mention that I find all of these document names confusing.
Maybe because some of them predate me, or predate me using a computer, I
do not know.

Therefore, I thought I should mention the names are described in
standards(7) along with the full documents they correspond to. I would
stick to the names listed there for consistency. That is what I have
done when making changes to the glibc and gnulib manuals.

Collin


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2025-12-22  0:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-20 16:17 Early POSIX versions seldom included in history sections Seth McDonald
2025-12-20 17:44 ` Alejandro Colomar
2025-12-21  8:17   ` Seth McDonald
2025-12-21 12:49     ` Alejandro Colomar
2025-12-22  0:58       ` Collin Funk [this message]
2025-12-23  3:56         ` Seth McDonald
2025-12-23 12:43           ` 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=87bjjrbae9.fsf@gmail.com \
    --to=collin.funk1@gmail.com \
    --cc=alx@kernel.org \
    --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.