linux-security-module.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: mtk.manpages@gmail.com, "Andrew G . Morgan" <morgan@kernel.org>
Cc: linux-security-module@vger.kernel.org
Subject: [PATCH 01/16] Manual pages: getcap.8, getpcaps.8, setcap.8: SEE ALSO: add capabilities(7)
Date: Thu, 16 Jul 2020 12:18:12 +0200	[thread overview]
Message-ID: <20200716101827.162793-1-mtk.manpages@gmail.com> (raw)

Signed-off-by: Michael Kerrisk (man-pages) <mtk.manpages@gmail.com>
---
 doc/getcap.8   | 1 +
 doc/getpcaps.8 | 1 +
 doc/setcap.8   | 1 +
 3 files changed, 3 insertions(+)

diff --git a/doc/getcap.8 b/doc/getcap.8
index 05ee9bb..0547ff9 100644
--- a/doc/getcap.8
+++ b/doc/getcap.8
@@ -31,4 +31,5 @@ https://bugzilla.kernel.org/buglist.cgi?component=libcap&list_id=1047723&product
 .SH "SEE ALSO"
 .BR cap_get_file (3),
 .BR cap_to_text (3),
+.BR capabilities (7),
 .BR setcap (8)
diff --git a/doc/getpcaps.8 b/doc/getpcaps.8
index b070a3c..53d342e 100644
--- a/doc/getpcaps.8
+++ b/doc/getpcaps.8
@@ -34,6 +34,7 @@ Displays output in a somewhat ugly legacy format.
 Displays usage in a legacy-like format but not quite so ugly in modern
 default terminal fonts.
 .SH SEE ALSO
+.BR capabilities (7),
 .BR capsh "(8), " setcap "(8) and " getcap (8).
 .br
 .SH AUTHOR
diff --git a/doc/setcap.8 b/doc/setcap.8
index 445ed03..da95afb 100644
--- a/doc/setcap.8
+++ b/doc/setcap.8
@@ -58,4 +58,5 @@ https://bugzilla.kernel.org/buglist.cgi?component=libcap&list_id=1047723&product
 .SH "SEE ALSO"
 .BR cap_from_text (3),
 .BR cap_get_file (3),
+.BR capabilities (7),
 .BR getcap (8)
-- 
2.26.2


             reply	other threads:[~2020-07-16 10:18 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-16 10:18 Michael Kerrisk (man-pages) [this message]
2020-07-16 10:18 ` [PATCH 02/16] Manual pages: cap_get_file.3, getcap.8, setcap.8: SEE ALSO: add user_namespaces(7) Michael Kerrisk (man-pages)
2020-07-16 10:18 ` [PATCH 03/16] Manual pages: setcap.8: Formatting fix: use bold for function name Michael Kerrisk (man-pages)
2020-07-16 10:18 ` [PATCH 04/16] Manual pages: cap_from_text.3: typo fix Michael Kerrisk (man-pages)
2020-07-16 10:18 ` [PATCH 05/16] Manual pages: cap_get_file.3, getcap.8, setcap.8: clarify "namespace" Michael Kerrisk (man-pages)
2020-07-16 10:18 ` [PATCH 06/16] Manual pages: cap_get_file.3: Remove stray macros that have no effect Michael Kerrisk (man-pages)
2020-07-16 10:18 ` [PATCH 07/16] Manual pages: cap_get_proc.3: s/UNCERTAIN/CAP_MODE_UNCERTAIN/ Michael Kerrisk (man-pages)
2020-07-16 10:18 ` [PATCH 08/16] Manual pages: cap_get_proc.3: formatting fix Michael Kerrisk (man-pages)
2020-07-16 10:18 ` [PATCH 09/16] Manual pages: capsh.1: spelling fixes Michael Kerrisk (man-pages)
2020-07-16 10:18 ` [PATCH 10/16] Manual pages: capsh.1: Remove stray .TP macro Michael Kerrisk (man-pages)
2020-07-16 10:18 ` [PATCH 11/16] Manual pages: capsh.1: Correct/update the Cap field example for /proc/PID/status Michael Kerrisk (man-pages)
2020-07-16 10:18 ` [PATCH 12/16] Manual pages: capsh.1: Update the capsh --decode example Michael Kerrisk (man-pages)
2020-07-16 10:18 ` [PATCH 13/16] Manual pages: capsh.1: Describe the argument of --secbits in more detail Michael Kerrisk (man-pages)
2020-07-16 10:18 ` [PATCH 14/16] pam_cap.c: Spelling fix in output string Michael Kerrisk (man-pages)
2020-07-16 10:18 ` [PATCH 15/16] Various source files: spelling fixes on comments Michael Kerrisk (man-pages)
2020-07-16 10:18 ` [PATCH 16/16] capsh.c: Spelling fixes in usage() message Michael Kerrisk (man-pages)
2020-07-16 15:08   ` Andrew G. Morgan
2020-07-17  6: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=20200716101827.162793-1-mtk.manpages@gmail.com \
    --to=mtk.manpages@gmail.com \
    --cc=linux-security-module@vger.kernel.org \
    --cc=morgan@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;
as well as URLs for NNTP newsgroup(s).