Linux Manual Pages development
 help / color / mirror / Atom feed
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Jakub Wilk <jwilk@jwilk.net>
Cc: "Helge Kreutzmann" <debian@helgefjell.de>,
	"Alejandro Colomar" <alx.manpages@gmail.com>,
	"Mario Blättermann" <mario.blaettermann@gmail.com>,
	linux-man@vger.kernel.org
Subject: Re: Issue in man page mount_namespaces.7
Date: Mon, 5 Dec 2022 06:36:41 -0600	[thread overview]
Message-ID: <20221205123641.3ctrtk7cnyzkotyn@illithid> (raw)
In-Reply-To: <20221205120305.htc2sd7r5qtvte5m@jwilk.net>

[-- Attachment #1: Type: text/plain, Size: 924 bytes --]

At 2022-12-05T13:03:05+0100, Jakub Wilk wrote:
> * Helge Kreutzmann <debian@helgefjell.de>, 2022-12-04 10:07:
> > Issue:    mount or unmount → mount or umount
> 
> The system call and the command line tool are written without "n" for
> historical reasons, but it's spelled "unmount" otherwise.
> 
> > "This mount shares events with members of a peer group.  Mount and unmount "
> > "events immediately under this mount will propagate to the other mounts that "
> > "are members of the peer group.  I<Propagation> here means that the same "
> > "mount or unmount will automatically occur under all of the other mounts in "
> > "the peer group.  Conversely, mount and unmount events that take place under "
> > "peer mounts will propagate to this mount."

Yes, let us please not entrench Thompson spelling reforms to English in
ordinary prose, lest we creat more problems than we solve.

Regards,
Branden

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2022-12-05 12:36 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
2022-12-05 12:03 ` Jakub Wilk
2022-12-05 12:20   ` Alejandro Colomar
2022-12-05 12:36   ` G. Branden Robinson [this message]
2022-12-05 12:37     ` 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: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 12:11 ` 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  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-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=20221205123641.3ctrtk7cnyzkotyn@illithid \
    --to=g.branden.robinson@gmail.com \
    --cc=alx.manpages@gmail.com \
    --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