From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Jean-Philippe MENGUAL <jpmengual@debian.org>
Cc: linux-man <linux-man@vger.kernel.org>
Subject: Re: Error in the nsenter.1 page
Date: Mon, 20 Apr 2020 10:37:38 +0200 [thread overview]
Message-ID: <CAKgNAkhNufmY1T191WADHF-Oeu4_KgYmAAQrumDuAc2x+ENL1A@mail.gmail.com> (raw)
In-Reply-To: <d14c92ee-ba52-5821-5cb5-c3b476055770@debian.org>
Hello Jean-Philippe
Bugs in that page need to be reported eolsewhere.
See http://man7.org/linux/man-pages/man1/nsenter.1.html#COLOPHON
Thanks,
Michael
On Mon, 20 Apr 2020 at 00:47, Jean-Philippe MENGUAL
<jpmengual@debian.org> wrote:
>
> Hi,
>
> Sorry for not producing a patch but I dont understand the syntax in the
> file. Here is the problematic string:
> Children will have a set of PID to process mappings separate from the
> .B nsenter
> process
> For further details, see
> .BR pid_namespaces (7)
> and
> the discussion of the
> .B CLONE_NEWPID
> flag in
> .B nsenter
> will fork by default if changing the PID namespace, so that the new program
> and its children share the same PID namespace and are visible to each other.
> If \fB\-\-no\-fork\fP is used, the new program will be exec'ed without
> forking.
>
> I think it is buggy. The "For further details, see..." seems at the
> middle of two sentences explaining the same thing, should be moved at
> the end of the paragraph I guess. I think I will try reordering the
> sentences in the translation to avoid keeping a fuzzy until the next
> release, but the translation will then be different from the English string.
>
> Thanks for your feedback
>
>
> Regards
>
> --
> Jean-Philippe MENGUAL
> Debian Developer non uploading
> Community team member
> Accessibility team member
> debian-l10n-french team member
> President of Debian France non-profit organization
>
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
prev parent reply other threads:[~2020-04-20 8:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-19 22:47 Error in the nsenter.1 page Jean-Philippe MENGUAL
2020-04-20 8:37 ` 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=CAKgNAkhNufmY1T191WADHF-Oeu4_KgYmAAQrumDuAc2x+ENL1A@mail.gmail.com \
--to=mtk.manpages@gmail.com \
--cc=jpmengual@debian.org \
--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 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).