From: Karel Zak <kzak@redhat.com>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: util-linux@vger.kernel.org
Subject: Re: [PATCH 2/2] Manual pages: unshare.1: clarify that --pid=<file> requires --fork
Date: Wed, 3 Jun 2020 17:06:36 +0200 [thread overview]
Message-ID: <20200603150636.g2kwxzwqc4ml4y63@ws.net.home> (raw)
In-Reply-To: <CAKgNAkgLZp=t21vrcfuf9iPmHxk_tG74-_jbtOftQKpGge1dpw@mail.gmail.com>
On Wed, Jun 03, 2020 at 12:22:46PM +0200, Michael Kerrisk (man-pages) wrote:
> > +(Creation of a persistent PID namespace will fail if the
> > +.B \-\-fork
> > +is not also specified.)
>
> Small wording problem there... s/is/option is/
Applied & fixed, thanks!
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
prev parent reply other threads:[~2020-06-03 15:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-03 7:40 [PATCH 1/2] Manual pages: unshare.1: clarify description and example for --mount=<path> Michael Kerrisk (man-pages)
2020-06-03 7:40 ` [PATCH 2/2] Manual pages: unshare.1: clarify that --pid=<file> requires --fork Michael Kerrisk (man-pages)
2020-06-03 10:22 ` Michael Kerrisk (man-pages)
2020-06-03 15:06 ` Karel Zak [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=20200603150636.g2kwxzwqc4ml4y63@ws.net.home \
--to=kzak@redhat.com \
--cc=mtk.manpages@gmail.com \
--cc=util-linux@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 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).