Skip to content

Commit f0d57f8

Browse files
committed
fixup! Instead of creating Cygwin symlinks, use deep copy by default
This adds the missing documentation (in case we ever publish the information about the MSYS variable on msys2.org). Signed-off-by: Johannes Schindelin <[email protected]>
1 parent 7484c55 commit f0d57f8

File tree

1 file changed

+9
-1
lines changed

1 file changed

+9
-1
lines changed

winsup/doc/cygwinenv.xml

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -104,7 +104,7 @@ back to the parent process.</para>
104104
</listitem>
105105

106106
<listitem>
107-
<para><envar>winsymlinks:{lnk,native,nativestrict,sys}</envar></para>
107+
<para><envar>winsymlinks:{lnk,native,nativestrict,sys,deepcopy}</envar></para>
108108

109109
<itemizedlist mark="square">
110110
<listitem>
@@ -133,6 +133,14 @@ system call will immediately fail.</para>
133133
plain files with the <literal>system</literal> attribute, containing a magic
134134
cookie followed by the path to which the link points.</para>
135135
</listitem>
136+
137+
<listitem>
138+
<para>If set to <literal>winsymlinks:deepcopy</literal>, a copy of the source
139+
will be created at the target (a "deep" copy in the case of directories, i.e.
140+
the source directory will be copied recursively). This mode makes a trade-off
141+
between compatibility and interoperability with Win32 programs, favoring the
142+
latter.</para>
143+
</listitem>
136144
</itemizedlist>
137145

138146
<para>Note that this setting has no effect where Cygwin knows that the

0 commit comments

Comments
 (0)