PlaneteCasio
/
libc
1
0
Fork 0
Code Issues 6 Pull Requests Releases Wiki Activity

* cygwinenv.sgml (cygwinenv-implemented-options): Try to make 

compatibility new symlinks vs. old Cygwin clearer.
This commit is contained in:
Corinna Vinschen 2010-01-12 16:40:53 +00:00
parent c04ed45d82
commit 4aab0ed828
2 changed files with 11 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
winsup/doc/ChangeLog
View File

@ -1,3 +1,8 @@
2010-01-12 Corinna Vinschen <corinna@vinschen.de>
* cygwinenv.sgml (cygwinenv-implemented-options): Try to make
compatibility new symlinks vs. old Cygwin clearer.
2010-01-10 Corinna Vinschen <corinna@vinschen.de>
* pathnames.sgml (mount-table): Add info that posix=0 is default for

10
winsup/doc/cygwinenv.sgml
View File

@ -142,10 +142,12 @@ variables. The current list of always uppercased variables is:</para>
symlinks as Windows shortcuts with a special header and the R/O attribute
set. If not set, Cygwin creates symlinks as plain files with a magic number,
a path and the system attribute set. Defaults to not set since plain
file symlinks are faster to write and faster to read. The new style of
plain file symlinks is incompatible with older Cygwin releases because
the new symlinks use UTF-16 to encode the target filename, while the
old symlinks used the current ANSI or OEM charset.</para>
file symlinks are faster to write and faster to read.</para>
<para>Please note that symlinks created under Cygwin 1.7 or later are
not readable by older Cygwin releases because the new symlinks use UTF-16
to encode the target filename, while the old symlinks used the current
ANSI or OEM charset.</para>
</listitem>
</itemizedlist>