zsh-workers
 help / color / mirror / code / Atom feed
From: Wesley <opndev@protonmail.com>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: zsh-workers@zsh.org
Subject: Re: The request of words matter updated
Date: Wed, 05 Oct 2022 03:02:37 +0000	[thread overview]
Message-ID: <1df0ee8a-e36f-4a6e-588c-626f5f867da0@protonmail.com> (raw)

On 10/4/22 03:05, Daniel Shahaf wrote:
> Wesley wrote on Mon, Oct 03, 2022 at 15:27:49 +0000:
>>
>> On 9/28/22 12:34, Peter Stephenson wrote:
>>
>>> Once that's established, perhaps someone could arrange for an online vote
>>> at one of the websites that do that?  Given no technical change results
>>> from any of this, opinion is all we've got, and there's evidently no
>>> sign of a consensus.
>>
>> Do you need consensus on this change? I mean, if someone provided a
>> patch that changes master/slave to something else that makes sense
>> because they want to stay clear of those words, would it not be
>> accepted?
>
> pws posted such a patch upthread.

I read the message, but didn't see the patch below it. My bad.

>> The change is essentially a refactor and should pass all the tests..
>
> Any change has costs.  In this case, the change might shadow or unshadow
> another symbol (pws checked that for the terms his patch uses), would be
> one more manual step for any future «blame» or «log» run, would
> necessitate a rebase for anyone who has local patches to zpty.c, and
> would introduce a https://xkcd.com/927/ problem to anyone reading zsh's
> pseudo-terminal module's C source file.

That is a thing, the linux man page are still using master and slave (as
stated in 50669).

A rebase for those who have custom patches.. it is a cost that they
already have since they have forked the project.

@Sunny (OP)
How is IBM treating the Linux manual page(s), either via RHEL/SUSE or
LinuxOne?

Cheers,
Wesley

--
Wesley Schwengle



             reply	other threads:[~2022-10-05  3:03 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-05  3:02 Wesley [this message]
2022-10-05  3:18 ` zeurkous
  -- strict thread matches above, loose matches on Subject: below --
2022-09-19  6:52 Xiao Ling XL Chen
2022-09-19 18:20 ` Bart Schaefer
2022-09-27  3:15   ` Lawrence Velázquez
2022-09-27  4:22     ` Bart Schaefer
2022-09-27  8:44       ` Peter Stephenson
2022-09-27 20:54         ` Daniel Shahaf
2022-09-27 21:15           ` Clinton Bunch
2022-09-27 21:22             ` Clinton Bunch
2022-09-27 21:32           ` Mikael Magnusson
2022-09-28  6:17             ` Felipe Contreras
2022-09-28  6:30               ` Ellenor Bjornsdottir
2022-09-29  8:23                 ` Lawrence Velázquez
2022-09-29  8:35             ` Axel Beckert
2022-09-28  6:14           ` Felipe Contreras
2022-09-28 12:16             ` Clinton Bunch
2022-09-28 16:34           ` Peter Stephenson
2022-10-03 14:25             ` Peter Stephenson
2022-10-03 23:24               ` Eric Cook
2022-10-04  0:45                 ` Wesley
2022-10-04  5:29               ` Daniel Shahaf
2022-10-04  5:48                 ` Daniel Shahaf
2022-10-04 11:14                 ` Peter Stephenson
2022-10-08 18:14                 ` Martijn Dekker
2022-10-03 15:27             ` Wesley
2022-10-04  7:05               ` Daniel Shahaf
2022-10-04  7:28                 ` Daniel Shahaf
2022-10-08  7:54                 ` Felipe Contreras
2022-10-08 10:46                   ` Mikael Magnusson
2022-09-29  8:31           ` Axel Beckert
2022-09-28 20:01         ` Eric Cook
2022-09-29  8:05           ` Lawrence Velázquez
2022-10-01  4:40     ` Lawrence Velázquez
2022-10-03 15:24       ` Peter Stephenson

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=1df0ee8a-e36f-4a6e-588c-626f5f867da0@protonmail.com \
    --to=opndev@protonmail.com \
    --cc=d.s@daniel.shahaf.name \
    --cc=zsh-workers@zsh.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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).