linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Wilk <jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org>
To: Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH] capabilities.7: spfix
Date: Mon, 29 Feb 2016 00:40:56 +0100	[thread overview]
Message-ID: <1456702856-6077-1-git-send-email-jwilk@jwilk.net> (raw)

Fix capitalization in the reference to section "Effect of user ID
changes on capabilities".

Capitalization of the section name was changed in
c634028ab5768a042196fd71a38088499b21de12, but the reference remained
unchanged.

Signed-off-by: Jakub Wilk <jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org>
---
 man7/capabilities.7 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/man7/capabilities.7 b/man7/capabilities.7
index 26de609..b4824ba 100644
--- a/man7/capabilities.7
+++ b/man7/capabilities.7
@@ -1096,7 +1096,7 @@ Setting this flag stops the kernel from adjusting capability sets when
 the thread's effective and filesystem UIDs are switched between
 zero and nonzero values.
 (See the subsection
-.IR "Effect of User ID Changes on Capabilities" .)
+.IR "Effect of user ID changes on capabilities" .)
 .TP
 .B SECBIT_NOROOT
 If this bit is set, then the kernel does not grant capabilities
-- 
2.7.0

--
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

             reply	other threads:[~2016-02-28 23:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-28 23:40 Jakub Wilk [this message]
     [not found] ` <1456702856-6077-1-git-send-email-jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org>
2016-02-29 11:23   ` [PATCH] capabilities.7: spfix 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=1456702856-6077-1-git-send-email-jwilk@jwilk.net \
    --to=jwilk-txgolizoknreowh0uzbu5w@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;
as well as URLs for NNTP newsgroup(s).