From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Cygwin generates syscalls for *.lnk files on filesystems with native symlink support?
Date: Mon, 8 Jan 2024 19:11:49 +0100 [thread overview]
Message-ID: <ZZw65R578QtNO_4E@calimero.vinschen.de> (raw)
In-Reply-To: <266017637.5531727.1704733902023@mail.yahoo.com>
On Jan 8 17:11, matthew patton via Cygwin wrote:
> > For instance: Getting rid of .lnk files isn't easy with backward compatibility in mind.
> screw backward compatability! :)Why carry around bandaids on bandaids
> for an OS that is 10 years out of support?
We're using .lnk files for FIFOs. That's the compat concern, not some OS
from the past.
> Obviously not ripe for 3.6 or maybe even 3.7, but at some point we
> should just put a stick in the sand and say this .lnk crap is dead and
> you have to either compile it back in with an IFDEF or a CYGWIN var.
No ifdefs, and a Cygwin var setting unfortunately exists.
> And while we're at it use OS-native links instead of Junctions. I'm
> not sure how that came about but Junctions are unhelpful.
Cygwin does not create symlinks as junctions. No idea where you got
that idea.
Corinna
next prev parent reply other threads:[~2024-01-08 18:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 4:23 Cedric Blancher
2023-09-01 10:57 ` Corinna Vinschen
2023-09-26 5:12 ` Cedric Blancher
2023-12-18 12:04 ` Cedric Blancher
2024-01-08 13:56 ` Corinna Vinschen
2024-01-08 17:11 ` matthew patton
2024-01-08 18:11 ` Corinna Vinschen [this message]
2024-01-08 18:44 ` matthew patton
2024-01-08 19:05 ` Rainer Emrich
2024-01-08 19:17 ` Jeffrey Altman
2024-01-08 19:21 ` Corinna Vinschen
2024-01-08 19:57 ` matthew patton
2024-01-08 20:27 ` Brian Inglis
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=ZZw65R578QtNO_4E@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).