public inbox for cygwin-patches@cygwin.com
 help / color / mirror / Atom feed
From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin-patches@cygwin.com
Subject: Re: [PATCH] Cygwin: pty: Rename input named pipes.
Date: Tue, 23 Mar 2021 09:38:08 +0900	[thread overview]
Message-ID: <20210323093808.0e0b4114dc72ca5e9ddaabc3@nifty.ne.jp> (raw)
In-Reply-To: <YFiEQJf6ZDivGbPH@calimero.vinschen.de>

On Mon, 22 Mar 2021 12:49:20 +0100
Corinna Vinschen wrote:
> Hi Takashi,
> 
> On Mar 21 12:59, Takashi Yano via Cygwin-patches wrote:
> > - Currently, the name of input pipe is "ptyNNNN-from-master" for
> >   cygwin process, and "ptyNNNN-to-slave" for non-cygwin process.
> >   These are not only inconsistent with output pipes but also very
> >   confusing.
> >   With this patch, these are renamed to "ptyNNNN-from-master-cyg"
> >   and "ptyNNNN-from-master" respectively.
> > ---
> >  winsup/cygwin/fhandler_tty.cc | 2 +-
> >  winsup/cygwin/tty.cc          | 4 ++--
> >  2 files changed, 3 insertions(+), 3 deletions(-)
> 
> Actually... wouldn't it make more sense to call the Cygwin pipe
> 
>   pty%d-from-master / pty%d-to-slave
> 
> and the non-Cygwin one something like
> 
>   pty%d-from-master-nat / pty%d-to-slave-nat
> 
> ?
> 
> After all, Cygwin is the norm, and non-Cygwin is the exception.
> 
> On second thought, this would also make sense for thr fhandler methods,
> i. e.
> 
>   get_output_handle / get_output_handle_cyg
> 
> vs.
> 
>   get_output_handle_nat / get_output_handle
> 
> Probably the fhandler stuff is too much renaming for this release,
> but we should do this for the next one, I think.

I basically agree. However, renaming them consistently is
too much for 3.2.0 release as you mentioned. So, IMHO, it
is better to apply this patch once for 3.2.0 release and
then fully rename them for the next one.

What do you think?

-- 
Takashi Yano <takashi.yano@nifty.ne.jp>

  reply	other threads:[~2021-03-23  0:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-21  3:59 Takashi Yano
2021-03-22 11:49 ` Corinna Vinschen
2021-03-23  0:38   ` Takashi Yano [this message]
2021-03-23  9:32     ` Corinna Vinschen
2021-03-23 11:49       ` 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=20210323093808.0e0b4114dc72ca5e9ddaabc3@nifty.ne.jp \
    --to=takashi.yano@nifty.ne.jp \
    --cc=cygwin-patches@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).