public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: stdin pipe rename in 3.2.0
Date: Fri, 19 Mar 2021 05:30:32 -0600	[thread overview]
Message-ID: <766c3567-346e-118a-778c-0ca8052228a5@SystematicSw.ab.ca> (raw)
In-Reply-To: <CAE6_+UdHjCdvsRA3GkA4g++OWJVUNocMdEUZsZ5YC7M+=hobkA@mail.gmail.com>

On 2021-03-19 01:53, Christoph Reiter via Cygwin wrote:
> On Fri, Mar 19, 2021 at 4:47 AM Brian Inglis wrote:
>> On 2021-03-18 14:28, Christoph Reiter via Cygwin wrote:
>> If these are being renamed should they not now use neutral terminology based on
>> terms such as primary and secondary, and the primary/default repo branches on a
>> term such as main?

> Yes. Though there are ~700 instances of such terms in the cygwin code
> so I'd suggest you propose this separately to the list.

I'm not suggesting anyone even attempt to do a mass clean up of such terms.

But as any area needs work where these terms are used, take the opportunity.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

  reply	other threads:[~2021-03-19 11:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-18 20:28 Christoph Reiter
2021-03-19  3:46 ` Brian Inglis
2021-03-19  7:53   ` Christoph Reiter
2021-03-19 11:30     ` Brian Inglis [this message]
2021-03-19 10:08 ` Takashi Yano
2021-03-19 10:16   ` Takashi Yano
2021-03-19 11:17   ` Christoph Reiter
2021-03-19 12:05   ` Takashi Yano
2021-03-19 12:58     ` Corinna Vinschen
2021-03-21  3:59       ` Takashi Yano

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=766c3567-346e-118a-778c-0ca8052228a5@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --cc=cygwin@cygwin.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 read-only IMAP folder(s) and NNTP newsgroup(s).