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 13:13:25 +0100 [thread overview]
Message-ID: <6eecf6fc-cb8e-38e5-fd65-beade207136e@gmail.com> (raw)
In-Reply-To: <20221204090710.GA347@Debian-50-lenny-64-minimal>
[-- Attachment #1.1: Type: text/plain, Size: 649 bytes --]
On 12/4/22 10:07, Helge Kreutzmann wrote:
> Without further ado, the following was found:
>
> Issue: unmounts → umounts
>
> "Note that a mount's propagation type determines whether mounts and unmounts"
> "of mounts I<immediately under> the mount are propagated. Thus, the"
> "propagation type does not affect propagation of events for grandchildren and"
> "further removed descendant mounts. What happens if the mount itself is"
> "unmounted is determined by the propagation type that is in effect for the"
> "I<parent> of the mount."
Fixed (and other identical cases). Thanks.
--
<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 12:13 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:13 ` Alejandro Colomar [this message]
-- 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: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 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 12:29 ` Alejandro Colomar
2022-12-04 9:07 Helge Kreutzmann
2022-12-04 9:07 Helge Kreutzmann
2022-12-04 9:07 Helge Kreutzmann
2022-12-04 12:11 ` Alejandro Colomar
2022-12-04 9:07 Helge Kreutzmann
2022-12-04 12:25 ` Alejandro Colomar
2022-12-04 14:00 ` Helge Kreutzmann
2022-12-04 14:06 ` Alejandro Colomar
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
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=6eecf6fc-cb8e-38e5-fd65-beade207136e@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