From: Seth McDonald <sethmcmail@pm.me>
To: Alejandro Colomar <alx@kernel.org>
Cc: Seth McDonald <sethmcmail@pm.me>, linux-man@vger.kernel.org
Subject: [PATCH v1 0/1] man/man2/semop.2: Fix VERSIONS and HISTORY mix-up
Date: Thu, 25 Dec 2025 07:26:02 +0000 [thread overview]
Message-ID: <cover.1766641592.git.sethmcmail@pm.me> (raw)
[-- Attachment #1: Type: text/plain, Size: 953 bytes --]
Hi all,
The man page for semop(2) and semtimedop(2) has a VERSIONS section, but
not a HISTORY section. However, the VERSIONS section describes what
should instead be in a HISTORY section, and doesn't distinguish between
the two functions' different history/versions.
The reason for this seems to be a commit which removed text attributing
the listed standards and versions to the corresponding function. I've
patched the page to make clear which function has what history.
Do note that this my first attempt at using a git & email workflow. So
while I've attempted to follow the contribution guidelines, there may
still be some errors I've missed, and which I'd be happy to correct.
Seth McDonald (1):
man/man2/semop.2: Rebrand VERSIONS as HISTORY
man/man2/semop.2 | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)
Range-diff against v0:
-: --------- > 1: 86b4c2ec9 man/man2/semop.2: Rebrand VERSIONS as HISTORY
--
2.47.3
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 322 bytes --]
next reply other threads:[~2025-12-25 7:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-25 7:26 Seth McDonald [this message]
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
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=cover.1766641592.git.sethmcmail@pm.me \
--to=sethmcmail@pm.me \
--cc=alx@kernel.org \
--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 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.