From: Eugene Syromyatnikov <evgsyr-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH 01/15] add_key.2, request_key.2, keyrings.7: update Linux documentation pointers
Date: Mon, 11 Sep 2017 05:03:50 +0200 [thread overview]
Message-ID: <20170911030350.GA29734@asgard.redhat.com> (raw)
In 4.13 release cycle, key management documentation has been reformatted
to ReStructured text and moved to a separate "keys" directory.
Relevant kernel commits: v4.13-rc1~34^2~27, v4.13-rc1~34^2~25
* man2/add_key.2 (.SH SEE ALSO): Amend pointers to
Documentation/security/keys.txt and Documentation/keys-request-key.txt
with changes introduced in Linux 4.13 (Documentation/keys/core.rst and
Documentation/keys/request-key.rst).
* man2/request_key.2 (.SH SEE ALSO): Likewise.
* man7/keyrings.7 (.SH SEE ALSO): Likewise.
Signed-off-by: Eugene Syromyatnikov <evgsyr-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
---
man2/add_key.2 | 8 +++++++-
man2/request_key.2 | 8 +++++++-
man7/keyrings.7 | 4 +++-
3 files changed, 17 insertions(+), 3 deletions(-)
diff --git a/man2/add_key.2 b/man2/add_key.2
index 2e67362..6417334 100644
--- a/man2/add_key.2
+++ b/man2/add_key.2
@@ -284,6 +284,12 @@ main(int argc, char *argv[])
.BR user\-session\-keyring (7)
.PP
The kernel source files
+.IR Documentation/security/keys/core.rst
+and
+.IR Documentation/keys/request\-key.rst
+(or, before Linux 4.13, in the files
+.\" commit b68101a1e8f0263dbc7b8375d2a7c57c6216fb76
.IR Documentation/security/keys.txt
and
-.IR Documentation/security/keys\-request\-key.txt .
+.\" commit 3db38ed76890565772fcca3279cc8d454ea6176b
+.IR Documentation/security/keys\-request\-key.txt ).
diff --git a/man2/request_key.2 b/man2/request_key.2
index ce987e3..e6a5c7d 100644
--- a/man2/request_key.2
+++ b/man2/request_key.2
@@ -561,6 +561,12 @@ main(int argc, char *argv[])
.BR request\-key (8)
.PP
The kernel source files
+.IR Documentation/security/keys/core.rst
+and
+.IR Documentation/keys/request\-key.rst
+(or, before Linux 4.13, in the files
+.\" commit b68101a1e8f0263dbc7b8375d2a7c57c6216fb76
.IR Documentation/security/keys.txt
and
-.IR Documentation/security/keys\-request\-key.txt .
+.\" commit 3db38ed76890565772fcca3279cc8d454ea6176b
+.IR Documentation/security/keys\-request\-key.txt ).
diff --git a/man7/keyrings.7 b/man7/keyrings.7
index 0cb1190..6f2581c 100644
--- a/man7/keyrings.7
+++ b/man7/keyrings.7
@@ -870,4 +870,6 @@ scripts can use them.
The kernel source files
.IR Documentation/crypto/asymmetric-keys.txt
and under
-.IR Documentation/security/keys .
+.IR Documentation/security/keys
+(or, before Linux 4.13, in the file
+.IR Documentation/security/keys.txt ).
--
2.1.4
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2017-09-11 3:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-11 3:03 Eugene Syromyatnikov [this message]
[not found] ` <20170911030350.GA29734-ZbobWygYI+YXGNroddHbYwC/G2K4zDHf@public.gmane.org>
2017-09-11 13:54 ` [PATCH 01/15] add_key.2, request_key.2, keyrings.7: update Linux documentation pointers Michael Kerrisk (man-opages)
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=20170911030350.GA29734@asgard.redhat.com \
--to=evgsyr-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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