From: David Macek <david.macek.0@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Symlink targets dereferenced when winsymlinks:native
Date: Thu, 19 Nov 2015 21:17:00 -0000 [thread overview]
Message-ID: <564E3C5B.10006@gmail.com> (raw)
In-Reply-To: <0D835E9B9CD07F40A48423F80D3B5A702E9519BE@USA7109MB022.na.xerox.net>
[-- Attachment #1: Type: text/plain, Size: 654 bytes --]
On 19. 11. 2015 20:36, Nellis, Kenneth wrote:
> FWIW, my results are different:
>
> $ printenv CYGWIN
> winsymlinks:nativestrict
> $ touch XXX
> $ ln -s XXX YYY
> $ ln -s YYY ZZZ
> $ ls -l
> total 0
> -rw-r----- 1 knellis Domain Users 0 Nov 19 14:28 XXX
> lrwxrwxrwx 1 knellis Domain Users 3 Nov 19 14:28 YYY -> XXX
> lrwxrwxrwx 1 knellis Domain Users 3 Nov 19 14:28 ZZZ -> YYY
> $ uname -svr
> CYGWIN_NT-6.1 2.3.1(0.291/5/3) 2015-11-14 12:44
> $
Weird. I also tried in the virtual root directory, in case cygdrive affects it, but no luck, still absolute paths.
I'm on Windows 10, if it makes any difference.
--
David Macek
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4254 bytes --]
next prev parent reply other threads:[~2015-11-19 21:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 22:28 David Macek
2015-11-18 17:55 ` Corinna Vinschen
2015-11-18 18:13 ` David Macek
2015-11-18 19:48 ` Corinna Vinschen
2015-11-18 20:01 ` Warren Young
2015-11-18 20:07 ` Corinna Vinschen
2015-11-19 18:53 ` David Macek
2015-11-19 19:36 ` Nellis, Kenneth
2015-11-19 21:17 ` David Macek [this message]
2015-11-20 9:26 ` Corinna Vinschen
2015-11-24 21:48 ` David Macek
2015-11-26 12:02 ` Corinna Vinschen
2015-11-29 14:10 ` David Macek
2015-11-29 17:10 ` Corinna Vinschen
2015-11-20 9:29 ` Corinna Vinschen
2015-11-24 19:51 ` David Macek
2015-11-25 3:20 ` Linda Walsh
2015-11-25 14:59 ` David Macek
2015-11-26 11:53 ` Another reason to not corrupt winnative symlinks: :currenly, they are linux-CIFS compat. Cygwin's are not Linda Walsh
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=564E3C5B.10006@gmail.com \
--to=david.macek.0@gmail.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).