From: Aleksa Sarai <cyphar@cyphar.com>
To: Al Viro <viro@zeniv.linux.org.uk>,
Michael Kerrisk <mtk.manpages@gmail.com>
Cc: Aleksa Sarai <cyphar@cyphar.com>,
Christian Brauner <christian@brauner.io>,
Aleksa Sarai <asarai@suse.de>,
linux-man@vger.kernel.org, linux-api@vger.kernel.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH man-pages v2 0/2] document openat2(2)
Date: Mon, 3 Feb 2020 02:19:05 +1100 [thread overview]
Message-ID: <20200202151907.23587-1-cyphar@cyphar.com> (raw)
Patch changelog:
v2:
* Updated based on the new (now-merged) structure layout and semantics.
v1: <https://lore.kernel.org/linux-man/20191206142931.28138-1-cyphar@cyphar.com/>
* Updated based on Kerrisk's review.
RFC: <https://lore.kernel.org/linux-man/20191003145542.17490-1-cyphar@cyphar.com/>
Now that openat2(2) has landed in Linus's tree[1], here is the
associated man-page changes to document it.
[1]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=b55eef872a96738ea9cb35774db5ce9a7d3a648f
Aleksa Sarai (2):
path_resolution.7: update to mention openat2(2) features
openat2.2: document new openat2(2) syscall
man2/open.2 | 17 ++
man2/openat2.2 | 471 +++++++++++++++++++++++++++++++++++++++++
man7/path_resolution.7 | 56 +++--
3 files changed, 526 insertions(+), 18 deletions(-)
create mode 100644 man2/openat2.2
--
2.25.0
next reply other threads:[~2020-02-02 15:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-02 15:19 Aleksa Sarai [this message]
2020-02-02 15:19 ` [PATCH man-pages v2 1/2] path_resolution.7: update to mention openat2(2) features Aleksa Sarai
2020-03-30 20:38 ` Michael Kerrisk (man-pages)
2020-02-02 15:19 ` [PATCH man-pages v2 2/2] openat2.2: document new openat2(2) syscall Aleksa Sarai
2020-03-30 9:08 ` Michael Kerrisk (man-pages)
2020-03-30 9:20 ` Aleksa Sarai
2020-03-30 9:36 ` Michael Kerrisk (man-pages)
2020-03-30 9:48 ` Aleksa Sarai
2020-03-30 20:43 ` Michael Kerrisk (man-pages)
2020-03-31 14:39 ` Aleksa Sarai
2020-04-01 6:38 ` Michael Kerrisk (man-pages)
2020-04-08 21:29 ` Michael Kerrisk (man-pages)
2020-04-12 16:49 ` Aleksa Sarai
2020-04-13 7:22 ` Michael Kerrisk (man-pages)
2020-04-14 10:35 ` Aleksa Sarai
2020-04-15 20:24 ` Michael Kerrisk (man-pages)
2020-05-04 10:17 ` Michael Kerrisk (man-pages)
2020-06-10 5:53 ` [PATCH] symlink.7: document magic-links more completely Aleksa Sarai
2020-06-19 13:00 ` Michael Kerrisk (man-pages)
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=20200202151907.23587-1-cyphar@cyphar.com \
--to=cyphar@cyphar.com \
--cc=asarai@suse.de \
--cc=christian@brauner.io \
--cc=linux-api@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/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).