cygpath -m behaviour change

[Christopher Faylor]

On Fri, Sep 13, 2013 at 01:17:05PM -0400, Robert Pendell wrote:
>On Fri, Sep 13, 2013 at 11:55 AM, David Griffiths <> wrote:
>> I reinstalled cygwin after a disk failure recently and one of my
>> scripts stopped working. The problem can be easily reproduced by
>> entering:
>>
>>     $ cygpath -m boo/..
>>     cygpath: error converting "boo/.." - No such file or directory
>>
>> this is with version 1.7.24(0.269/5/3). On another machine with 1.7.17
>> installed, the same command results in "./".
>>
>> I can workaround by using backslashes instead of forward slashes but
>> other people might find their scripts broken as well.
>>
>> Cheers,
>>
>> Dave
>>
>
>I believe this behavior was changed in 1.7.22
>
>See this thread for more information but basically it was changed to
>conform /.. path checking to posix standards.
>
>http://cygwin.com/ml/cygwin/2013-05/msg00222.html

Yes, that's exactly right, assuming that 'boo' doesn't exist.

cgf

--
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