public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Native symbolic link behavior is broken and makes backups using Cygwin command line tools impossible
Date: Mon, 04 Jan 2021 18:58:26 +0100	[thread overview]
Message-ID: <87pn2k8tz1.fsf@Rainer.invalid> (raw)
In-Reply-To: <CAC+X2=L-sBmgi_OoFVjJtpPp6MszHGH8ycEiOo4V1NNbWDAP-A@mail.gmail.com> (Matt D. via Cygwin's message of "Mon, 4 Jan 2021 10:27:09 -0500")

Matt D. via Cygwin writes:
> The normal behavior for both Windows and Linux is to create the
> symbolic link whether the target exists or not.

That's not the case on Windows or rather it has restrictions that can
trip you up.  On Windows you must specify if the symbolic link points to
a directory or a file in order to create a symbolic link to a
non-existing file.  If that information is not available, it is
obviously safer to not create the symbolic link.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

      parent reply	other threads:[~2021-01-04 17:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-03  4:16 Matt D.
2021-01-03  5:00 ` Brian Inglis
2021-01-04 10:36   ` Matt D.
2021-01-04 12:30     ` Eliot Moss
2021-01-04 15:27       ` Matt D.
2021-01-04 15:46         ` Jeffrey Altman
2021-01-12 17:59           ` Matt D.
2021-01-12 22:18             ` Andrey Repin
2021-01-14  0:09               ` Matt D.
2021-01-04 16:32         ` Eliot Moss
2021-01-04 17:58         ` Achim Gratz [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=87pn2k8tz1.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --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).