From: Alejandro Colomar <alx@kernel.org>
To: Jakub Wilk <jwilk@jwilk.net>
Cc: "Helge Kreutzmann" <debian@helgefjell.de>,
"Mario Blättermann" <mario.blaettermann@gmail.com>,
linux-man@vger.kernel.org
Subject: Re: Issue in man page mount_namespaces.7
Date: Wed, 1 Nov 2023 18:06:31 +0100 [thread overview]
Message-ID: <ZUKFl6ylEBOv_uNQ@debian> (raw)
In-Reply-To: <20231101162310.u4b46gii47yjhsgt@jwilk.net>
[-- Attachment #1: Type: text/plain, Size: 784 bytes --]
On Wed, Nov 01, 2023 at 05:23:10PM +0100, Jakub Wilk wrote:
> * Alejandro Colomar <alx@kernel.org>, 2023-11-01 16:57:
> > On Wed, Nov 01, 2023 at 02:02:11PM +0000, Helge Kreutzmann wrote:
> > > Without further ado, the following was found:
> > >
> > > Issue: mount point → mount ?
> >
> > I'm not sure that improves significantly. Is there any difference
> > between a 'mount' and a 'mount point'?
>
> We discussed it last year:
> https://lore.kernel.org/linux-man/20221205123809.5p66jmpalhd4bhoq@jwilk.net/
Hi Jakub!
Thanks for reminding of that exact message. I don't feel qualified to
edit that paragraph. If anyone else want to review the change, feel
invited.
Thanks,
Alex
>
> --
> Jakub Wilk
--
<https://www.alejandro-colomar.es/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-11-01 17:06 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 14:02 Issue in man page mount_namespaces.7 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 [this message]
-- strict thread matches above, loose matches on Subject: below --
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:13 ` 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: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=ZUKFl6ylEBOv_uNQ@debian \
--to=alx@kernel.org \
--cc=debian@helgefjell.de \
--cc=jwilk@jwilk.net \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).