From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Gleb Fotengauer-Malinovskiy
<glebfm-u2l5PoMzF/Vg9hUCZPvPmw@public.gmane.org>,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Subject: Re: [PATCH] umount.2: fix typo
Date: Sat, 04 Apr 2015 09:42:23 +0100 [thread overview]
Message-ID: <551FA3EF.4070303@gmail.com> (raw)
In-Reply-To: <20150401161012.GA16041-N9aU+Tdk7XkoO014n+3aBsY9il7ykmry@public.gmane.org>
On 04/01/2015 05:10 PM, Gleb Fotengauer-Malinovskiy wrote:
> Signed-off-by: Gleb Fotengauer-Malinovskiy <glebfm-u2l5PoMzF/Vg9hUCZPvPmw@public.gmane.org>
Thanks, Gleb. Applied.
Cheers,
Michael
> ---
> man2/umount.2 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/man2/umount.2 b/man2/umount.2
> index 149da1a..7c4452a 100644
> --- a/man2/umount.2
> +++ b/man2/umount.2
> @@ -164,7 +164,7 @@ are available in glibc since version 2.11.
> These functions are Linux-specific and should not be used in
> programs intended to be portable.
> .SH NOTES
> -.SS umount() amd shared mount points
> +.SS umount() and shared mount points
> Shared mount points cause any mount activity on a mount point, including
> .BR umount (2)
> operations, to be forwarded to every shared mount point in the
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
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
prev parent reply other threads:[~2015-04-04 8:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 16:10 [PATCH] umount.2: fix typo Gleb Fotengauer-Malinovskiy
[not found] ` <20150401161012.GA16041-N9aU+Tdk7XkoO014n+3aBsY9il7ykmry@public.gmane.org>
2015-04-04 8:42 ` Michael Kerrisk (man-pages) [this message]
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=551FA3EF.4070303@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=glebfm-u2l5PoMzF/Vg9hUCZPvPmw@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@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).