From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Gleb Fotengauer-Malinovskiy
<glebfm-u2l5PoMzF/Vg9hUCZPvPmw@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] unshare.2: fix unbalanced parentheses
Date: Sat, 08 Aug 2015 10:07:11 +0200 [thread overview]
Message-ID: <55C5B8AF.3090800@gmail.com> (raw)
In-Reply-To: <20150808080356.GA7347-N9aU+Tdk7XkoO014n+3aBsY9il7ykmry@public.gmane.org>
Thanks, Gleb. Applied.
Cheers,
Michael
On 08/08/2015 10:04 AM, Gleb Fotengauer-Malinovskiy wrote:
> ---
> man2/unshare.2 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/man2/unshare.2 b/man2/unshare.2
> index 42b2d0e..5d1c235 100644
> --- a/man2/unshare.2
> +++ b/man2/unshare.2
> @@ -50,7 +50,7 @@ _BSD_SOURCE || _SVID_SOURCE
> .SH DESCRIPTION
> .BR unshare ()
> allows a process (or thread) to disassociate parts of its execution
> -context that are currently being shared with other processes or threads).
> +context that are currently being shared with other processes (or threads).
> Part of the execution context, such as the mount namespace, is shared
> implicitly when a new process is created using
> .BR fork (2)
>
--
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-08-08 8:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-08 8:04 [PATCH] unshare.2: fix unbalanced parentheses Gleb Fotengauer-Malinovskiy
[not found] ` <20150808080356.GA7347-N9aU+Tdk7XkoO014n+3aBsY9il7ykmry@public.gmane.org>
2015-08-08 8:07 ` 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=55C5B8AF.3090800@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).