From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Misbehaviour of cygpath -am between versions 3.1.4 and 3.3.2
Date: Wed, 17 Nov 2021 19:29:29 +0100 [thread overview]
Message-ID: <YZVKCbpo6ySiCwOv@calimero.vinschen.de> (raw)
In-Reply-To: <14910218332.20211117194454@yandex.ru>
On Nov 17 19:44, Andrey Repin via Cygwin wrote:
> Greetings, Wolfgang S. Kechel!
>
> > The command 'cygpath -am .' yields different results between
> > cygwin-3.1.4-1 and cygwin-3.3.2-1 on a Windows 10 box when the current
> > directory is a network share.
>
> > Example with V3.1.4:
>
> > cygpath -am . ---> P:/mytool/gbuild/wintel/libtiff
>
> > Example with V3.3.2-1
>
> > cygpath -am . ---> //mynas.mydomain.de/product/mytool/gbuild/wintel/libtiff
>
> I'm pretty sure there was a discussion about it earlier.
>
> > This causes UNC filenames to appear and this cmd.exe is unable to start
> > in those directories when started from a cygwin shell or from nmake run
> > in a cygwin shell.
>
> cmd.exe can be configured to STFU.
Apparently default starting with Windows 11...
Corinna
prev parent reply other threads:[~2021-11-17 18:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 14:41 Wolfgang S. Kechel
2021-11-17 16:44 ` Andrey Repin
2021-11-17 18:29 ` Corinna Vinschen [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=YZVKCbpo6ySiCwOv@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--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).