From: Alejandro Colomar <alx@kernel.org>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: Helge Kreutzmann <debian@helgefjell.de>,
mario.blaettermann@gmail.com, linux-man@vger.kernel.org,
branden@debian.org
Subject: Re: Issue in man page getpt.3
Date: Thu, 25 Dec 2025 22:20:17 +0100 [thread overview]
Message-ID: <aU2ptq23PUlRC8d5@devuan> (raw)
In-Reply-To: <20251225210533.3xqjtrwkwsl27zbg@illithid>
[-- Attachment #1: Type: text/plain, Size: 1969 bytes --]
Hi Branden,
On Thu, Dec 25, 2025 at 03:05:33PM -0600, G. Branden Robinson wrote:
> Hi Alex,
>
> At 2025-12-25T14:22:54+0100, Alejandro Colomar wrote:
> > On Thu, Dec 25, 2025 at 02:20:39PM +0100, Alejandro Colomar wrote:
> > > On Wed, Dec 24, 2025 at 02:38:26PM +0000, Helge Kreutzmann wrote:
> > > > Without further ado, the following was found:
> > > >
> > > > Issue: multiplexor → multiplexer
> > >
> > > I see both used:
> > >
> > > $ grep -rho multiplex.r man/ | sort| uniq -c
> > > 4 multiplexer
> > > 4 multiplexor
> > >
> > > Which one should we prefer, and why?
> >
> > A reason for 'e' is that __NR_multiplexer uses 'e'.
>
> That's the best reason to choose 'e', and the one I'd select.
Agree. Thanks!
commit 011bcb9c453cbf6490f7678e8d2f880acf2026f7 (HEAD -> contrib)
Author: Alejandro Colomar <alx@kernel.org>
Date: Thu Dec 25 22:15:32 2025 +0100
man/: Unify spelling of 'multiplexer'
Both 'o' and 'e' are used in the manual pages:
$ grep -rho multiplex.r man/ | sort| uniq -c
4 multiplexer
4 multiplexor
Let's stick to 'e', for consistency with __NR_multiplexer.
Reported-by: Helge Kreutzmann <debian@helgefjell.de>
Acked-by: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Signed-off-by: Alejandro Colomar <alx@kernel.org>
>
> The question of usage of -or or -er is a messy one in English, whether
> in Commonwealth or Yankee forms.[1][2]
>
> (If we're being even more picky, -trix further spices the mix.[3])
:-)
>
> Regards,
> Branden
>
> [1] https://separatedbyacommonlanguage.blogspot.com/2007/10/agentive-suffixes-er-and-or-and-little.html
> [2] https://ianjamesparsley.wordpress.com/2023/02/17/the-weirdness-of-agent-nouns/
> [3] https://www.cjr.org/language_corner/womens_suffixes.php
Thanks!
Have a lovely night!
Alex
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-12-25 21:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-24 14:38 Issue in man page getpt.3 Helge Kreutzmann
2025-12-25 13:20 ` Alejandro Colomar
2025-12-25 13:22 ` Alejandro Colomar
2025-12-25 21:05 ` G. Branden Robinson
2025-12-25 21:20 ` Alejandro Colomar [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-08-24 14:48 Helge Kreutzmann
2025-08-31 16:36 ` Alejandro Colomar
2025-08-31 16:53 ` 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=aU2ptq23PUlRC8d5@devuan \
--to=alx@kernel.org \
--cc=branden@debian.org \
--cc=debian@helgefjell.de \
--cc=g.branden.robinson@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.