From: "Štěpán Němec" <stepnem@gmail.com>
To: linux-man@vger.kernel.org,
Alejandro Colomar <alx.manpages@gmail.com>,
Michael Kerrisk <mtk.manpages@gmail.com>
Subject: [PATCH] namespaces.7: fix confusion caused by text reorganization
Date: Tue, 13 Jul 2021 21:26:08 +0200 [thread overview]
Message-ID: <20210713192608.3804441-1-stepnem@gmail.com> (raw)
Since commit ee81d7e41852, the flags list has been (only) above, not
below, these references.
(The flags table was added even before that, in commit
0b497138b908 ("namespaces.7: Add table of namespaces to top of page"))
Fixes: ee81d7e41852 ("namespaces.7: Include manual page references in the summary table of namespace types")
Signed-off-by: Štěpán Němec <stepnem@gmail.com>
---
man7/namespaces.7 | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/man7/namespaces.7 b/man7/namespaces.7
index d35c2d383e32..0ac32c77e21c 100644
--- a/man7/namespaces.7
+++ b/man7/namespaces.7
@@ -97,7 +97,7 @@ If the
.I flags
argument of the call specifies one or more of the
.B CLONE_NEW*
-flags listed below, then new namespaces are created for each flag,
+flags listed above, then new namespaces are created for each flag,
and the child process is made a member of those namespaces.
(This system call also implements a number of features
unrelated to namespaces.)
@@ -119,7 +119,7 @@ If the
.I flags
argument of the call specifies one or more of the
.B CLONE_NEW*
-flags listed below, then new namespaces are created for each flag,
+flags listed above, then new namespaces are created for each flag,
and the calling process is made a member of those namespaces.
(This system call also implements a number of features
unrelated to namespaces.)
base-commit: 33248cfe50ebb8762208e7ef3264676dad71b016
--
2.32.0.rc1.27.g991a26804f1e
next reply other threads:[~2021-07-13 19:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-13 19:26 Štěpán Němec [this message]
2021-07-14 20:22 ` [PATCH] namespaces.7: fix confusion caused by text reorganization Alejandro Colomar (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=20210713192608.3804441-1-stepnem@gmail.com \
--to=stepnem@gmail.com \
--cc=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
/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