DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:mime-version
	:content-type:content-transfer-encoding; q=dns; s=default; b=Byf
	2asZtaqmottKIDborTMz02Bbfq1Zsv3djz1k2NXdUdD1279rfubXQMmVw+KyjcnL
	O6VJd6ryu1QGfBt5LJqJFWG2J1vdeDAs+f2Kp46vHB91XWEe068J8c85rS8SigXA
	soL7OIpZgDZDT90TQKOYwDjll5cbvjb7KpnPbHRc=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: Chevallier Yves <YChevallier@etel.ch>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: cygpath compatiblity break (v2.1 -> v2.7)
Date: Thu, 13 Apr 2017 12:34:28 +0000
Message-ID: <69c9334669c0420f88c515e77756880c@de01ex22.GLOBAL.JHCN.NET>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 8bit

I get a very different behaviour with `cygpath` after I upgrade my version of Cygwin. Why? and how can I fix it?

With Cygwin 2.7:

```
$ uname -a
CYGWIN_NT-6.1-WOW CPT 2.7.0(0.306/5/3) 2017-02-12 13:13 i686 Cygwin
$ cygpath --version
cygpath (cygwin) 2.7.0

$ cd  /
$ touch foo.exe
$ cygpath -m foo
foo.exe

$ cd
$ touch foo.exe
$ cygpath -m foo
foo
```

With Cygwin 2.1:
```
$ uname -a
CYGWIN_NT-6.1-WOW CPT 2.1.0(0.287/5/3) 2015-07-14 21:26 i686 Cygwin
$ cygpath --version
cygpath (cygwin) 2.1.0

$ cd /
$ touch foo.exe
$ cygpath -m foo
foo

$ cd
$ touch foo.exe
$ cygpath -m foo
foo
```


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple