From: Alejandro Colomar <alx@kernel.org>
To: linux-man@vger.kernel.org
Cc: Alejandro Colomar <alx@kernel.org>,
aalbersh@kernel.org, linux-api@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: [RFC v2 0/8] Add at(2) manual page, and refer to it
Date: Sat, 7 Nov 2026 13:47:39 +0100 [thread overview]
Message-ID: <cover.1794055492.git.alx@kernel.org> (raw)
In-Reply-To: <c93cb32f5d7f4473bdf51465037f1a010348b705.1792776993.git.alx@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 2092 bytes --]
Hi!
Here's a draft of a patch set for adding a centralized at(2) manual page
and using it elsewhere to:
- De-duplicate documentation about *at() system calls.
- Make the slight differences more obvious.
- Have a central specification of how new *at() system calls should
look like, so that differences don't grow unnecessarily.
- Try to remove the unnecessary differences, if we can.
Have a lovely day!
Alex
Alejandro Colomar (8):
man/man3const/_ATFILE_SOURCE.3const: Add page
man/man2/at.2: Add link page
man/man2/chown.2: Refer to at(2)
man/man2/mount_setattr.2: Refer to at(2)
man/man2/open_tree.2: Refer to at(2)
man/man2/rename.2: Refer to at(2)
man/man3const/_ATFILE_SOURCE.3const: Some functions report ESRCH
instead of EACCES
man/man2/utimensat.2: Refer to at(2)
man/man2/at.2 | 1 +
man/man2/chown.2 | 114 ++-----------------
man/man2/mount_setattr.2 | 66 +++--------
man/man2/open_tree.2 | 168 ++-------------------------
man/man2/rename.2 | 84 +-------------
man/man2/utimensat.2 | 141 ++---------------------
man/man3const/_ATFILE_SOURCE.3const | 170 ++++++++++++++++++++++++++++
7 files changed, 214 insertions(+), 530 deletions(-)
create mode 100644 man/man2/at.2
create mode 100644 man/man3const/_ATFILE_SOURCE.3const
Range-diff against v1:
-: ------------ > 1: 39bf4d24176a man/man3const/_ATFILE_SOURCE.3const: Add page
-: ------------ > 2: 56086d43dbe4 man/man2/at.2: Add link page
-: ------------ > 3: 7fdc286a682a man/man2/chown.2: Refer to at(2)
-: ------------ > 4: c206656df161 man/man2/mount_setattr.2: Refer to at(2)
-: ------------ > 5: 4e8ce7b9cf9d man/man2/open_tree.2: Refer to at(2)
-: ------------ > 6: 8a5ac3f93ba5 man/man2/rename.2: Refer to at(2)
-: ------------ > 7: 8ae17f3f6863 man/man3const/_ATFILE_SOURCE.3const: Some functions report ESRCH instead of EACCES
-: ------------ > 8: 3de33c76083e man/man2/utimensat.2: Refer to at(2)
--
2.55.0
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-11-07 12:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-23 17:40 [RFC v1] man/man2/at.2: Add page Alejandro Colomar
2026-10-23 17:42 ` Alejandro Colomar
2026-10-23 17:45 ` Alejandro Colomar
2026-10-26 12:27 ` Andrey Albershteyn
2026-10-26 15:42 ` Alejandro Colomar
2026-10-27 8:10 ` Andrey Albershteyn
2026-11-07 12:47 ` Alejandro Colomar [this message]
2026-11-07 12:47 ` [RFC v2 1/8] man/man3const/_ATFILE_SOURCE.3const: " Alejandro Colomar
2026-11-07 12:47 ` [RFC v2 2/8] man/man2/at.2: Add link page Alejandro Colomar
2026-11-07 12:47 ` [RFC v2 3/8] man/man2/chown.2: Refer to at(2) Alejandro Colomar
2026-11-07 12:48 ` [RFC v2 4/8] man/man2/mount_setattr.2: " Alejandro Colomar
2026-11-09 16:07 ` Andrey Albershteyn
2026-11-07 12:48 ` [RFC v2 5/8] man/man2/open_tree.2: " Alejandro Colomar
2026-11-09 16:12 ` Andrey Albershteyn
2026-11-07 12:48 ` [RFC v2 6/8] man/man2/rename.2: " Alejandro Colomar
2026-11-07 12:48 ` [RFC v2 7/8] man/man3const/_ATFILE_SOURCE.3const: Some functions report ESRCH instead of EACCES Alejandro Colomar
2026-11-07 12:48 ` [RFC v2 8/8] man/man2/utimensat.2: Refer to at(2) 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.1794055492.git.alx@kernel.org \
--to=alx@kernel.org \
--cc=aalbersh@kernel.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox