public inbox for cygwin-patches@cygwin.com
 help / color / mirror / Atom feed
From: David Macek <david.macek.0@gmail.com>
To: cygwin-patches@cygwin.com
Subject: [PATCH] Add a section describing peculiarities of how Cygwin creates NTFS symlinks
Date: Tue, 24 Nov 2015 22:59:00 -0000	[thread overview]
Message-ID: <5654EBB5.7070100@gmail.com> (raw)
In-Reply-To: <20151118200719.GW6402@calimero.vinschen.de>

[-- Attachment #1: Type: text/plain, Size: 1133 bytes --]

First take on how to describe dereferencing of Cygwin-only symlinks path components when creating NTFS symlinks.

Note that I haven't tried building the documentation, so I don't know if the added paragraph breaks anything. Hopefully not.

	* pathnames.xml: Add a section describing peculiarities
	of how Cygwin creates NTFS symlinks

---
 winsup/doc/pathnames.xml | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/winsup/doc/pathnames.xml b/winsup/doc/pathnames.xml
index cdbf9fa..9077303 100644
--- a/winsup/doc/pathnames.xml
+++ b/winsup/doc/pathnames.xml
@@ -407,6 +407,9 @@ these two settings, see <xref linkend="using-cygwinenv"></xref>.
 On AFS, native symlinks are the only supported type of symlink due to
 AFS lacking support for DOS attributes.  This is independent from the
 <literal>winsymlinks</literal> setting.</para>
+<para>Creation of native symlinks follows special rules to ensure the links
+are usable outside of Cygwin. This includes dereferencing any Cygwin-only
+symlinks that lie in the target path.</para>
 </listitem>
 
 <listitem>
-- 
2.6.2.windows.1

-- 
David Macek


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4254 bytes --]

           reply	other threads:[~2015-11-24 22:59 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20151118200719.GW6402@calimero.vinschen.de>]

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=5654EBB5.7070100@gmail.com \
    --to=david.macek.0@gmail.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).