From: Carlos O'Donell <carlos@redhat.com>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>,
"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>,
linux-man <linux-man@vger.kernel.org>, enh <enh@google.com>,
Zack Weinberg <zackw@panix.com>
Cc: Florian Weimer <fweimer@redhat.com>,
Paul Eggert <eggert@cs.ucla.edu>,
Joseph Myers <joseph@codesourcery.com>,
Linux API <linux-api@vger.kernel.org>
Subject: Re: [RFC PATCH] Replacing "master-slave" terminology for pseudoterminals
Date: Thu, 30 Jul 2020 07:38:02 -0400 [thread overview]
Message-ID: <c690ad2f-5f3c-5a8b-7b4c-ad29976aeab0@redhat.com> (raw)
In-Reply-To: <cbf7666c-440e-b4bd-0ff6-712123845fae@gmail.com>
On 7/30/20 5:16 AM, Michael Kerrisk (man-pages) wrote:
> I know what you mean. One reason for that verbosity is the need to
> clearly distinguish "pseudoterminal device/end" from "pseudoterminal
> device pair". It's hard to avoid being wordy there.
The perfect is the enemy of the good. My feeling is that as others
write this text in emails or discussions, we'll eventually all settle
on some other short form we find agreeable and then later we can adjust
the man pages to use that. Until then taking the lead to change this
language is the correct way forward.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2020-07-30 11:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 10:39 [RFC PATCH] Replacing "master-slave" terminology for pseudoterminals Michael Kerrisk (man-pages)
2020-07-29 10:47 ` Michael Kerrisk (man-pages)
2020-07-30 4:06 ` Carlos O'Donell
2020-07-30 9:16 ` Michael Kerrisk (man-pages)
2020-07-30 11:38 ` Carlos O'Donell [this message]
2020-07-30 20:35 ` enh
2020-07-31 7:48 ` Michael Kerrisk (man-pages)
2020-08-04 17:25 ` enh
2020-08-04 20:04 ` Michael Kerrisk (man-pages)
[not found] ` <CAJgzZopP=O1cZ2M=3h6Q-X08+eVMPQE_zOCnsEjN=hUTHOkYwQ@mail.gmail.com>
2020-07-30 9:16 ` Michael Kerrisk (man-pages)
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=c690ad2f-5f3c-5a8b-7b4c-ad29976aeab0@redhat.com \
--to=carlos@redhat.com \
--cc=eggert@cs.ucla.edu \
--cc=enh@google.com \
--cc=fweimer@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=zackw@panix.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 NNTP newsgroup(s).