From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-patches@cygwin.com
Subject: Re: [PATCH 0/3] Add more winsymlinks values
Date: Wed, 21 Jul 2021 10:19:15 +0200 [thread overview]
Message-ID: <YPfYgz0EHe7Yw5ko@calimero.vinschen.de> (raw)
In-Reply-To: <20210719163134.9230-1-jon.turney@dronecode.org.uk>
On Jul 19 17:31, Jon Turney wrote:
> I'm not sure this is the best idea, since it adds more configurations that
> aren't going to get tested often, but the idea is that this would enable
> proper and consistent control of the symlink type used from setup, as
> discussed in [1].
>
> [1] https://cygwin.com/pipermail/cygwin-apps/2021-May/041327.html
Why isn't it sufficient to use 'winsymlinks:native' from setup?
The way we express symlinks shouldn't be a user choice, really. The
winsymlinks thingy was only ever introduced in a desperate attempt to
improve access to symlinks from native tools, and I still don't see a
way around that. But either way, what's the advantage in allowing the
user complete control over the type, even if the type is only useful in
Cygwin?
Corinna
next prev parent reply other threads:[~2021-07-21 8:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-19 16:31 Jon Turney
2021-07-19 16:31 ` [PATCH 1/3] Rename WSYM_sysfile to WSM_default Jon Turney
2021-07-19 16:31 ` [PATCH 2/3] Add winsymlinks:magic Jon Turney
2021-07-19 16:31 ` [PATCH 3/3] Add winsymlinks:wslstrict Jon Turney
2021-07-21 8:19 ` Corinna Vinschen [this message]
2021-07-21 10:24 ` [PATCH 0/3] Add more winsymlinks values Christian Franke
2021-07-22 8:03 ` Corinna Vinschen
2021-07-22 13:53 ` Jon Turney
2021-07-22 14:21 ` Corinna Vinschen
2021-07-28 19:55 ` Jon Turney
2021-07-29 10:23 ` Corinna Vinschen
2021-07-29 10:40 ` Corinna Vinschen
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=YPfYgz0EHe7Yw5ko@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--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).