From: Alejandro Colomar <alx.manpages@gmail.com>
To: Helge Kreutzmann <debian@helgefjell.de>
Cc: mario.blaettermann@gmail.com, linux-man@vger.kernel.org
Subject: Re: Issue in man page mount_namespaces.7
Date: Sun, 4 Dec 2022 15:06:40 +0100 [thread overview]
Message-ID: <4a2140e0-4589-87f3-e579-5575aab5e284@gmail.com> (raw)
In-Reply-To: <20221204140009.GD441@Debian-50-lenny-64-minimal>
[-- Attachment #1.1: Type: text/plain, Size: 1489 bytes --]
Hi Helge,
On 12/4/22 15:00, Helge Kreutzmann wrote:
> Hello Alejandro,
> On Sun, Dec 04, 2022 at 01:25:07PM +0100, Alejandro Colomar wrote:
>> On 12/4/22 10:07, Helge Kreutzmann wrote:
>>> Without further ado, the following was found:
>>>
>>> Issue: mount point I<B> → mount I<B>
>>>
>>> "Here, I<B> is the destination mount, and I<b> is a subdirectory path under"
>>> "the mount point I<B>. The propagation type of the resulting mount, I<B/b>,"
>>> "follows the same rules as for a bind mount, where the propagation type of"
>>> "the source mount is considered always to be private."
>>
>> I'm not sure about this one. If we change that wording, I'd like to make
>> sure we don't lose any details in the information. Please CC any related
>> kernel developers, and suggest them review the documentation for more
>> consistent language.
>
> Until recently, there was "mount point" used all over this man pages.
> This was changed to "mount" in one of the previous release of man
> pages.
I didn't know that; please point to the commit that did that.
>
> Thus I assumed that this one might have been overlooked.
Maybe.
>
> I mark it WONTFIX for now, so it doesn't get reported again and maybe
> you can clarify (if necessary) this in a later release.
If you point me to the patch, I can dig into it. Thanks!
>
> Thanks!
>
> Greetings
>
> Helge
>
>
Cheers,
Alex
--
<http://www.alejandro-colomar.es/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-12-04 14:06 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-04 9:07 Issue in man page mount_namespaces.7 Helge Kreutzmann
2022-12-04 12:25 ` Alejandro Colomar
2022-12-04 14:00 ` Helge Kreutzmann
2022-12-04 14:06 ` Alejandro Colomar [this message]
2022-12-04 14:14 ` Helge Kreutzmann
2022-12-04 21:26 ` Alejandro Colomar
2022-12-05 12:38 ` Jakub Wilk
2022-12-05 13:18 ` Alejandro Colomar
2022-12-05 18:54 ` Helge Kreutzmann
2022-12-05 21:12 ` Alejandro Colomar
-- strict thread matches above, loose matches on Subject: below --
2024-11-17 10:46 Helge Kreutzmann
2024-11-17 11:21 ` Alejandro Colomar
2024-11-17 22:27 ` Alejandro Colomar
2023-11-01 14:02 Helge Kreutzmann
2023-11-01 15:57 ` Alejandro Colomar
2023-11-01 16:22 ` Helge Kreutzmann
2023-11-01 16:23 ` Jakub Wilk
2023-11-01 17:06 ` Alejandro Colomar
2023-01-22 19:31 Helge Kreutzmann
2023-01-22 19:31 Helge Kreutzmann
2023-01-22 19:54 ` G. Branden Robinson
2023-01-22 20:01 ` Helge Kreutzmann
2023-01-22 20:18 ` G. Branden Robinson
2023-01-22 19:31 Helge Kreutzmann
2023-01-22 20:10 ` Alejandro Colomar
2023-01-22 20:27 ` Helge Kreutzmann
2023-01-22 20:54 ` Alejandro Colomar
2022-12-04 9:07 Helge Kreutzmann
2022-12-04 9:07 Helge Kreutzmann
2022-12-04 12:29 ` Alejandro Colomar
2022-12-04 9:07 Helge Kreutzmann
2022-12-04 12:11 ` Alejandro Colomar
2022-12-04 9:07 Helge Kreutzmann
2022-12-04 9:07 Helge Kreutzmann
2022-12-04 12:13 ` Alejandro Colomar
2022-12-04 9:07 Helge Kreutzmann
2022-12-04 12:13 ` Alejandro Colomar
2022-12-05 12:03 ` Jakub Wilk
2022-12-05 12:20 ` Alejandro Colomar
2022-12-05 12:36 ` G. Branden Robinson
2022-12-05 12:37 ` Alejandro Colomar
2022-03-13 12:34 Helge Kreutzmann
2022-03-13 12:34 Helge Kreutzmann
2022-03-13 12:34 Helge Kreutzmann
2022-03-13 12:34 Helge Kreutzmann
2022-03-13 12:34 Helge Kreutzmann
2022-03-13 12:34 Helge Kreutzmann
2022-03-13 12:34 Helge Kreutzmann
2022-03-13 12:34 Helge Kreutzmann
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=4a2140e0-4589-87f3-e579-5575aab5e284@gmail.com \
--to=alx.manpages@gmail.com \
--cc=debian@helgefjell.de \
--cc=linux-man@vger.kernel.org \
--cc=mario.blaettermann@gmail.com \
/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