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: spawn: Treat empty path as the current directory.
Date: Tue, 5 Jul 2022 13:54:36 +0900	[thread overview]
Message-ID: <20220705135436.1d91baa3426e31114938f51d@nifty.ne.jp> (raw)
In-Reply-To: <4ba56b80-8faa-de1b-f3c4-f64106797106@cornell.edu>

On Mon, 4 Jul 2022 19:05:19 -0400
Ken Brown wrote:
> On 7/4/2022 4:37 AM, Corinna Vinschen wrote:
> > On Jul  1 21:32, Ken Brown wrote:
> >> I interpreted the existing comment as meaning that a decision was already
> >> made at some point to align with Linux.  But it can't hurt to wait for
> >> Corinna to weigh in.
> > 
> > Personally I don't like this old crufty feature and I would rather keep
> > this POSIX compatible, but in fact it was meant to work as on Linux, so,
> > please go ahead, Takashi.
> > 
> > However, maybe this should go into the master branch only? WDYT?
> 
> I think so.  The bug has been around for a long time, and the code is tricky. 
> So we probably shouldn't take a chance on de-stabilizing the 3.3 branch.

Thanks! I have pushed the patch to master branch.

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

      reply	other threads:[~2022-07-05  4:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-27 12:44 Takashi Yano
2022-06-30 15:45 ` Ken Brown
2022-06-30 18:35   ` [EXTERNAL] " Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2022-06-30 19:03     ` Brian Inglis
2022-06-30 19:04     ` Takashi Yano
2022-07-01  1:16   ` Ken Brown
2022-07-01 23:31     ` Takashi Yano
2022-07-02  1:32       ` Ken Brown
2022-07-04  8:37         ` Corinna Vinschen
2022-07-04 23:05           ` Ken Brown
2022-07-05  4:54             ` Takashi Yano [this message]

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=20220705135436.1d91baa3426e31114938f51d@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).