From: Jakub Wilk <jwilk@jwilk.net>
To: Michael Kerrisk <mtk.manpages@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: [PATCH] mount_namespaces.7: tfix
Date: Fri, 11 Oct 2019 22:58:11 +0200 [thread overview]
Message-ID: <20191011205811.3214-1-jwilk@jwilk.net> (raw)
Remove duplicated word.
Signed-off-by: Jakub Wilk <jwilk@jwilk.net>
---
man7/mount_namespaces.7 | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/man7/mount_namespaces.7 b/man7/mount_namespaces.7
index 2447e3067..5c5d3f6c0 100644
--- a/man7/mount_namespaces.7
+++ b/man7/mount_namespaces.7
@@ -1097,7 +1097,7 @@ An application that creates a new mount namespace directly using
or
.BR unshare (2)
may desire to prevent propagation of mount events to other mount namespaces
-(as is is done by
+(as is done by
.BR unshare (1)).
This can be done by changing the propagation type of
mount points in the new namespace to either
--
2.23.0
next reply other threads:[~2019-10-12 5:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-11 20:58 Jakub Wilk [this message]
2019-10-11 21:46 ` [PATCH] mount_namespaces.7: tfix 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=20191011205811.3214-1-jwilk@jwilk.net \
--to=jwilk@jwilk.net \
--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;
as well as URLs for NNTP newsgroup(s).