From: Alejandro Colomar <alx@kernel.org>
To: Seth McDonald <sethmcmail@pm.me>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH v1 1/1] man/man2/semop.2: Rebrand VERSIONS as HISTORY
Date: Thu, 25 Dec 2025 12:39:05 +0100 [thread overview]
Message-ID: <aU0hq-ApW1SR8zjY@devuan> (raw)
In-Reply-To: <86b4c2ec94334aadcc8abc9f17b34b60716d399b.1766641593.git.sethmcmail@pm.me>
[-- Attachment #1: Type: text/plain, Size: 2474 bytes --]
On Thu, Dec 25, 2025 at 07:26:25AM +0000, Seth McDonald wrote:
> Rename the VERSIONS section to HISTORY, split semop(2) and semtimedop(2)
> in this section, and move the previously listed standards/versions to
> the corresponding functions.
>
> The VERSIONS section is really a HISTORY section that seems to have
> mixed up semop(2) and semtimedop(2). The relevant commit (4131356cdab8)
> removed some context specifying which standards/versions apply to
> semtimedop(2) only, causing this mix-up. The diff for this commit on
> man/man2/semop.2 is given below.
>
> $ git diff -U1 4131356cdab8^! man2/semop.2
> diff --git a/man2/semop.2 b/man2/semop.2
> index 7a1416a26..fe2906be4 100644
> --- a/man2/semop.2
> +++ b/man2/semop.2
> @@ -357,11 +357,8 @@ .SH ERRORS
> .IR semval .
> -.SH VERSIONS
> -.BR semtimedop ()
> -first appeared in Linux 2.5.52,
> -and was subsequently backported into Linux 2.4.22.
> -glibc support for
> -.BR semtimedop ()
> -first appeared in Linux 2.3.3.
> .SH STANDARDS
> -POSIX.1-2001, POSIX.1
> -2008, SVr4.
> +POSIX.1-2008.
> +.SH VERSIONS
> +Linux 2.5.52 (backported into Linux 2.4.22),
> +glibc 2.3.3.
> +POSIX.1-2001, SVr4.
> .\" SVr4 documents additional error conditions EINVAL, EFBIG, ENOSPC.
>
> The removed information is restored on account of the semop(2) and
> semtimedop(2) functions being described separately under HISTORY,
> removing the mix-up.
>
> Fixes: 4131356cdab8 (2023-03-17; "man*/, man-pages.7: VERSIONS, STANDARDS, HISTORY: Reorganize sections")
> Signed-off-by: Seth McDonald <sethmcmail@pm.me>
> ---
> man/man2/semop.2 | 10 ++++++++--
> 1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/man/man2/semop.2 b/man/man2/semop.2
> index 1e8213cbc..1b45e8e35 100644
> --- a/man/man2/semop.2
> +++ b/man/man2/semop.2
> @@ -349,10 +349,16 @@ .SH ERRORS
> .IR semval .
> .SH STANDARDS
> POSIX.1-2024.
> -.SH VERSIONS
> +.SH HISTORY
> +.TP
> +.BR semop ()
> +SVr4,
> +POSIX.1-2001.
> +.TP
> +.BR semtimedop ()
> +SVr4,
> Linux 2.5.52 (backported into Linux 2.4.22)
> ,
The patch is corrupt here. I wonder why this line is special. :)
> glibc 2.3.3.
> -POSIX.1-2001, SVr4.
> .\" SVr4 documents additional error conditions EINVAL, EFBIG, ENOSPC.
> .SH NOTES
> The
> --
> 2.47.3
>
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-12-25 11:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-25 7:26 [PATCH v1 0/1] man/man2/semop.2: Fix VERSIONS and HISTORY mix-up Seth McDonald
2025-12-25 7:26 ` [PATCH v1 1/1] man/man2/semop.2: Rebrand VERSIONS as HISTORY Seth McDonald
2025-12-25 11:39 ` Alejandro Colomar [this message]
2025-12-25 11:36 ` [PATCH v1 0/1] man/man2/semop.2: Fix VERSIONS and HISTORY mix-up Alejandro Colomar
2025-12-30 6:10 ` Seth McDonald
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=aU0hq-ApW1SR8zjY@devuan \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).