From fbc3d3efce9d1d513455ae2ce06f5ad3bb6d93f4 Mon Sep 17 00:00:00 2001 From: Bill Zissimopoulos Date: Mon, 19 Sep 2016 15:11:01 -0700 Subject: [PATCH] Update Changelog --- doc/Changelog.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/Changelog.adoc b/doc/Changelog.adoc index 4d1eba21..78758b08 100644 --- a/doc/Changelog.adoc +++ b/doc/Changelog.adoc @@ -7,7 +7,7 @@ This release brings support for reparse points and symbolic links as well as oth - Reparse points are a general mechanism for attaching special behavior to files. Symbolic links in Windows are implemented as reparse points. WinFsp supports any kind of reparse point including symbolic links. - The WinFsp FUSE implementation supports symbolic links. It also supports POSIX special files (FIFO, SOCK, CHR, BLK) as NFS reparse points (see https://msdn.microsoft.com/en-us/library/dn617178.aspx). -- User mode file systems that wish to support reparse points will have to set the `FSP_FSCTL_VOLUME_PARAMS::ReparsePoints` flag and implement the `FSP_FILE_SYSTEM_INTERFACE` methods `ResolveReparsePoints`, `GetReparsePoint`, `SetReparsePoint`, `DeleteReparsePoint`. +- User mode file systems that wish to support reparse points will have to set the `FSP_FSCTL_VOLUME_PARAMS::ReparsePoints` flag and implement the `FSP_FILE_SYSTEM_INTERFACE` methods `ResolveReparsePoints`, `GetReparsePoint`, `SetReparsePoint`, `DeleteReparsePoint`. More information in this blog article: http://www.secfs.net/winfsp/blog/files/reparse-points-symlinks-api-changes.html - The installation now includes public symbol files for all WinFsp components shipped.