From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Jakub Wilk <jwilk@jwilk.net>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org
Subject: Re: [PATCH] clone.2: tfix
Date: Sat, 9 Nov 2019 12:55:40 +0100 [thread overview]
Message-ID: <e4af85ae-a712-4a4b-c9e8-ab13c7569140@gmail.com> (raw)
In-Reply-To: <20191109085046.704-1-jwilk@jwilk.net>
On 11/9/19 9:50 AM, Jakub Wilk wrote:
> Remove duplicated word.
Um -- wow. That was quick! Patch applied.
Thanks,
Michael
> Signed-off-by: Jakub Wilk <jwilk@jwilk.net>
> ---
> man2/clone.2 | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/man2/clone.2 b/man2/clone.2
> index 02422b82f..db1ab586a 100644
> --- a/man2/clone.2
> +++ b/man2/clone.2
> @@ -78,7 +78,7 @@ context are shared between the calling process and the child process.
> For example, using these system calls, the caller can control whether
> or not the two processes share the virtual address space,
> the table of file descriptors, and the table of signal handlers.
> -These system system calls also allow the new child process to placed
> +These system calls also allow the new child process to placed
> in separate
> .BR namespaces (7).
> .PP
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2019-11-09 11:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-09 8:50 [PATCH] clone.2: tfix Jakub Wilk
2019-11-09 11:55 ` Michael Kerrisk (man-pages) [this message]
2020-03-05 21:35 Krzysztof Małysa
2020-03-12 8:14 ` Michael Kerrisk (man-pages)
2021-01-18 21:12 [patch] " Johannes Wellhöfer
2021-01-19 8:02 ` Michael Kerrisk (man-pages)
2021-04-19 20:01 [PATCH] " Johannes Berg
2021-04-19 22:17 ` Alejandro Colomar (man-pages)
2021-05-09 21:38 [PATCH] fflush.3: SEE ALSO: Add fpurge(3) Alejandro Colomar
2021-05-09 21:39 ` [PATCH] clone.2: tfix Alejandro Colomar
2021-05-09 23:17 ` 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=e4af85ae-a712-4a4b-c9e8-ab13c7569140@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=jwilk@jwilk.net \
--cc=linux-man@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.