From: Xiao Ling XL Chen <chenxlxl@cn.ibm.com>
To: "zsh-users@zsh.org" <zsh-users@zsh.org>
Cc: Kui K Zhang <kzzhang@cn.ibm.com>
Subject: Re: The request of words matter updated
Date: Tue, 27 Sep 2022 02:14:18 +0000 [thread overview]
Message-ID: <DM6PR15MB41393B8B2F8B0C52C54730B0F0559@DM6PR15MB4139.namprd15.prod.outlook.com> (raw)
In-Reply-To: <DM6PR15MB4139085983BB9582B84DDB3DF04D9@DM6PR15MB4139.namprd15.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 2341 bytes --]
Hello all!
I wanted to contact zsh-workers@zsh.org<mailto:zsh-workers@zsh.org> for the request of words matter updated but didn’t get any response. If zsh-users@zsh.org<mailto:zsh-users@zsh.org> isn’t correct one either, please let me know the right one. Thanks.
--------------------------------------------------------------------------------------------------------------
There 12 slave and 16 master used as variables in source code "Src/Modules/zpty.c". Even though the words "slave" & "master" are used as internal static variables, and not be exposed to external calling or exported it in message, as what the words matter requirement of our company, may I ask change them in a future level? For example, replace “slave” with "worker", "child", "helper", "replica", "follower", or "secondary [server, node, process, or other noun]", and replace “master” with "controller", "leader", "manager", "main", "coordinator", "parent", or "primary [server, node, process, or other noun]". Thanks.
Take care, stay strong, and stay safe.
Best regards,
Sunny (Xiao Ling Chen, 陈小玲)
z/OS USS SU&DBX Development and L3
IBM China Systems & Technology Lab (CSTL)
Tel: 86-010-82452454
E-mail: chenxlxl@cn.ibm.com<mailto:chenxlxl@cn.ibm.com>
--
From: Xiao Ling XL Chen <chenxlxl@cn.ibm.com>
Date: Monday, September 19, 2022 at 14:52
To: zsh-workers@zsh.org <zsh-workers@zsh.org>
Subject: The request of words matter updated
There 12 slave and 16 master used as variables in source code "Src/Modules/zpty.c". Even though the words "slave" & "master" are used as internal static variables, and not be exposed to external calling or exported it in message, as what the words matter requirement, may I ask change them in a future level? For example, replace “slave” with "worker", "child", "helper", "replica", "follower", or "secondary [server, node, process, or other noun]", and replace “master” with "controller", "leader", "manager", "main", "coordinator", "parent", or "primary [server, node, process, or other noun]". Thanks.
Take care, stay strong, and stay safe.
Best regards,
Sunny (Xiao Ling Chen, 陈小玲)
z/OS USS SU&DBX Development and L3
IBM China Systems & Technology Lab (CSTL)
Tel: 86-010-82452454
E-mail: chenxlxl@cn.ibm.com<mailto:chenxlxl@cn.ibm.com>
--
[-- Attachment #2: Type: text/html, Size: 11365 bytes --]
next parent reply other threads:[~2022-09-27 2:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DM6PR15MB4139085983BB9582B84DDB3DF04D9@DM6PR15MB4139.namprd15.prod.outlook.com>
2022-09-27 2:14 ` Xiao Ling XL Chen [this message]
2022-09-27 2:32 ` Lawrence Velázquez
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=DM6PR15MB41393B8B2F8B0C52C54730B0F0559@DM6PR15MB4139.namprd15.prod.outlook.com \
--to=chenxlxl@cn.ibm.com \
--cc=kzzhang@cn.ibm.com \
--cc=zsh-users@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).