All of lore.kernel.org
 help / color / mirror / Atom feed
From: Seth McDonald <seth.i.mcdonald@gmail.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: Seth McDonald <sethmcmail@pm.me>, linux-man@vger.kernel.org
Subject: [PATCH v1 00/15] man/man3type/*: Update history of types A-INTN
Date: Tue,  6 Jan 2026 17:07:49 +1000	[thread overview]
Message-ID: <cover.1767675322.git.sethmcmail@pm.me> (raw)

Hello again!

My next few patch sets should update datatypes in the 3type section.
There are 48 patches total for this section, though I will be
partitioning them into three separate sets according to alphabetical
order.  This is primarily based on Linux's documentation recommending
patch sets of at most ~15 patches.[1]  But if this mailing list has
different preferences, let me know and I'll adjust accordingly.

This patch set regards types whose identifiers start with A-INTN (case
insensitive, of course).

Regarding the order of the listed standards in HISTORY sections, I've
seen man pages with the same set of standards listed in different
orders.  But I have found a general ordering that a good number of pages
adhere to.  That being:

SVrX, X.XBSD, SUSvX, POSIX.1-YYYY, POSIX.2, Linux X.X, glibc X.X[.X],
others (e.g. OpenBSD, Solaris, AIX).

I call this a 'general' ordering because very rarely (if ever) are all
seven standards/systems listed (excluding 'others').  But subsets of
them tend to follow their relative ordering above, at least from what
I've seen.  So for consistency, I tended to use this ordering when
adding/updating standards.  That is, listing SUS and POSIX.1 after SV
and BSD, and before Linux, glibc, and other systems.

I also followed a few more guidelines when editing these lists that may
be noteworthy:
- Since POSIX and SUS merged into the same document in POSIX.1-2001/
  SUSv3, only POSIX.1-2001 is listed for functions in these standards
  (or later), but with XSI appended if the function was part of the XSI
  extension (e.g. POSIX.1-2008 XSI).
- Since SUSv1 is aligned with POSIX.1-1990,[2] if a function's first
  POSIX appearance was in POSIX.1-1988 or POSIX.1-1990, then it's first
  appearance in SUSv1 is not also listed due to being implied by its
  POSIX appearance.
- Similarly, since SUSv2 is aligned with POSIX.1-1996,[3] the same is
  true for functions first appearing in POSIX.1-1996 and SUSv2.

So in general, SUS is listed if the function (or constant/type) appeared
in SUSv1 or SUSv2 before it appeared in POSIX.1.

[1] <https://www.kernel.org/doc/Documentation/process/submitting-patches.rst>
[2] X/Open CAE Specification, System Interfaces and Headers Issue 4,
Version 2, Chapter 1.6 "Relationship to Formal Standards", p. 10.
[3] CAE Specification, System Interfaces and Headers, Issue 5, Chapter
1.6 "Relationship to Formal Standards", p. 11.

Seth McDonald (15):
  man/man3type/aiocb.3type: HISTORY: Update first POSIX appearance of
    aiocb(3type)
  man/man3type/blk{cnt,size}_t.3type: HISTORY: Update first SUS
    appearance of blk{cnt,size}_t(3type)
  man/man3type/cc_t.3type: HISTORY: Update first POSIX appearance of
    types
  man/man3type/clockid_t.3type: HISTORY: Update first POSIX appearance
    of clockid_t(3type)
  man/man3type/clock_t.3type: HISTORY: Update first POSIX appearance of
    clock_t(3type)
  man/man3type/dev_t.3type: HISTORY: Update first POSIX appearance of
    dev_t(3type)
  man/man3type/div_t.3type: HISTORY: Split [l]div_t(3type) and
    {ll,imax}div_t(3type)
  man/man3type/div_t.3type: HISTORY: Update first SUS appearance of
    [l]div_t(3type)
  man/man3type/FILE.3type: HISTORY: Update first POSIX appearance of
    FILE(3type)
  man/man3type/id_t.3type: HISTORY: Split id_t(3type) from
    [pug]id_t(3type)
  man/man3type/id_t.3type: HISTORY: Update first POSIX appearance of
    [pug]id_t(3type)
  man/man3type/id_t.3type: HISTORY: Mention change in datatypes of
    [pug]id_t(3type)
  man/man3type/id_t.3type: HISTORY: Update first POSIX appearance of
    id_t(3type)
  man/man3type/intN_t.3type: HISTORY: Split types and macros
  man/man3type/intN_t.3type: HISTORY: Update first SUS appearance of
    [u]intN_t(3type)

 man/man3type/FILE.3type      |  3 ++-
 man/man3type/aiocb.3type     |  2 +-
 man/man3type/blkcnt_t.3type  |  1 +
 man/man3type/blksize_t.3type |  1 +
 man/man3type/cc_t.3type      |  2 +-
 man/man3type/clock_t.3type   |  3 ++-
 man/man3type/clockid_t.3type |  2 +-
 man/man3type/dev_t.3type     |  2 +-
 man/man3type/div_t.3type     | 11 +++++++++++
 man/man3type/id_t.3type      | 22 +++++++++++++++++++++-
 man/man3type/intN_t.3type    | 20 ++++++++++++++++++++
 11 files changed, 62 insertions(+), 7 deletions(-)

Range-diff against v0:
 -:  ------------ >  1:  9d2453196924 man/man3type/aiocb.3type: HISTORY: Update first POSIX appearance of aiocb(3type)
 -:  ------------ >  2:  3e3cdf605fad man/man3type/blk{cnt,size}_t.3type: HISTORY: Update first SUS appearance of blk{cnt,size}_t(3type)
 -:  ------------ >  3:  eb523868fce1 man/man3type/cc_t.3type: HISTORY: Update first POSIX appearance of types
 -:  ------------ >  4:  75786342c4cc man/man3type/clockid_t.3type: HISTORY: Update first POSIX appearance of clockid_t(3type)
 -:  ------------ >  5:  24395294f63b man/man3type/clock_t.3type: HISTORY: Update first POSIX appearance of clock_t(3type)
 -:  ------------ >  6:  2bb3f33e65b7 man/man3type/dev_t.3type: HISTORY: Update first POSIX appearance of dev_t(3type)
 -:  ------------ >  7:  417e53f6394a man/man3type/div_t.3type: HISTORY: Split [l]div_t(3type) and {ll,imax}div_t(3type)
 -:  ------------ >  8:  feb8d662b9fe man/man3type/div_t.3type: HISTORY: Update first SUS appearance of [l]div_t(3type)
 -:  ------------ >  9:  77b4c360910f man/man3type/FILE.3type: HISTORY: Update first POSIX appearance of FILE(3type)
 -:  ------------ > 10:  18896b1be985 man/man3type/id_t.3type: HISTORY: Split id_t(3type) from [pug]id_t(3type)
 -:  ------------ > 11:  d32b6148d2a9 man/man3type/id_t.3type: HISTORY: Update first POSIX appearance of [pug]id_t(3type)
 -:  ------------ > 12:  00eec0f9aa43 man/man3type/id_t.3type: HISTORY: Mention change in datatypes of [pug]id_t(3type)
 -:  ------------ > 13:  e5992856df9c man/man3type/id_t.3type: HISTORY: Update first POSIX appearance of id_t(3type)
 -:  ------------ > 14:  903b6a6dee42 man/man3type/intN_t.3type: HISTORY: Split types and macros
 -:  ------------ > 15:  43f013547fbe man/man3type/intN_t.3type: HISTORY: Update first SUS appearance of [u]intN_t(3type)
-- 
2.47.3


             reply	other threads:[~2026-01-06  7:09 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-06  7:07 Seth McDonald [this message]
2026-01-06  7:07 ` [PATCH v1 01/15] man/man3type/aiocb.3type: HISTORY: Update first POSIX appearance of aiocb(3type) Seth McDonald
2026-01-06 13:56   ` Alejandro Colomar
2026-01-06  7:07 ` [PATCH v1 02/15] man/man3type/blk{cnt,size}_t.3type: HISTORY: Update first SUS appearance of blk{cnt,size}_t(3type) Seth McDonald
2026-01-06 13:57   ` Alejandro Colomar
2026-01-06  7:07 ` [PATCH v1 03/15] man/man3type/cc_t.3type: HISTORY: Update first POSIX appearance of types Seth McDonald
2026-01-06 13:57   ` Alejandro Colomar
2026-01-06  7:07 ` [PATCH v1 04/15] man/man3type/clockid_t.3type: HISTORY: Update first POSIX appearance of clockid_t(3type) Seth McDonald
2026-01-06 13:57   ` Alejandro Colomar
2026-01-06  7:07 ` [PATCH v1 05/15] man/man3type/clock_t.3type: HISTORY: Update first POSIX appearance of clock_t(3type) Seth McDonald
2026-01-06 13:58   ` Alejandro Colomar
2026-01-06  7:07 ` [PATCH v1 06/15] man/man3type/dev_t.3type: HISTORY: Update first POSIX appearance of dev_t(3type) Seth McDonald
2026-01-06 13:58   ` Alejandro Colomar
2026-01-06  7:07 ` [PATCH v1 07/15] man/man3type/div_t.3type: HISTORY: Split [l]div_t(3type) and {ll,imax}div_t(3type) Seth McDonald
2026-01-06 14:03   ` Alejandro Colomar
2026-01-06  7:07 ` [PATCH v1 08/15] man/man3type/div_t.3type: HISTORY: Update first SUS appearance of [l]div_t(3type) Seth McDonald
2026-01-06  7:07 ` [PATCH v1 09/15] man/man3type/FILE.3type: HISTORY: Update first POSIX appearance of FILE(3type) Seth McDonald
2026-01-06 14:06   ` Alejandro Colomar
2026-01-06  7:07 ` [PATCH v1 10/15] man/man3type/id_t.3type: HISTORY: Split id_t(3type) from [pug]id_t(3type) Seth McDonald
2026-01-06 14:07   ` Alejandro Colomar
2026-01-06  7:08 ` [PATCH v1 11/15] man/man3type/id_t.3type: HISTORY: Update first POSIX appearance of [pug]id_t(3type) Seth McDonald
2026-01-06 14:07   ` Alejandro Colomar
2026-01-06  7:08 ` [PATCH v1 12/15] man/man3type/id_t.3type: HISTORY: Mention change in datatypes " Seth McDonald
2026-01-06 14:12   ` Alejandro Colomar
2026-01-07  1:54     ` Collin Funk
2026-01-07  2:08     ` Seth McDonald
2026-01-07  7:55       ` Alejandro Colomar
2026-01-06  7:08 ` [PATCH v1 13/15] man/man3type/id_t.3type: HISTORY: Update first POSIX appearance of id_t(3type) Seth McDonald
2026-01-06  7:08 ` [PATCH v1 14/15] man/man3type/intN_t.3type: HISTORY: Split types and macros Seth McDonald
2026-01-06 14:16   ` Alejandro Colomar
2026-01-06  7:08 ` [PATCH v1 15/15] man/man3type/intN_t.3type: HISTORY: Update first SUS appearance of [u]intN_t(3type) Seth McDonald
2026-01-06 14:17   ` Alejandro Colomar
2026-01-06 12:34 ` [PATCH v1 00/15] man/man3type/*: Update history of types A-INTN Alejandro Colomar
2026-01-06 14:18   ` Alejandro Colomar
2026-01-07  3:33   ` Seth McDonald
2026-01-07  7:57     ` 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=cover.1767675322.git.sethmcmail@pm.me \
    --to=seth.i.mcdonald@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.