summaryrefslogtreecommitdiff
path: root/WHATSNEW.txt
diff options
context:
space:
mode:
authorJeremy Allison <jra@samba.org>2017-11-29 13:22:25 -0800
committerVolker Lendecke <vl@samba.org>2017-11-30 19:32:21 +0100
commit54b3706a776753a77a8ad97c599133300cff69e6 (patch)
treed8584a15cba82051ad2c46ea591b9017054172e9 /WHATSNEW.txt
parentabbc9b9ab793d22bca6a37828f4375ef38c56dd3 (diff)
downloadsamba-54b3706a776753a77a8ad97c599133300cff69e6.tar.gz
WHATSNEW: Explain reversal of smbclient symlink parameters against Windows server.
BUG: https://bugzilla.samba.org/show_bug.cgi?id=13172 Signed-off-by: Jeremy Allison <jra@samba.org> Reviewed-by: Volker Lendecke <vl@samba.org> Autobuild-User(master): Volker Lendecke <vl@samba.org> Autobuild-Date(master): Thu Nov 30 19:32:21 CET 2017 on sn-devel-144
Diffstat (limited to 'WHATSNEW.txt')
-rw-r--r--WHATSNEW.txt11
1 files changed, 11 insertions, 0 deletions
diff --git a/WHATSNEW.txt b/WHATSNEW.txt
index 4265627d774..9a7547e4e29 100644
--- a/WHATSNEW.txt
+++ b/WHATSNEW.txt
@@ -87,6 +87,17 @@ assumptions. Samba implements async I/O based on threads by default,
there is no special module required to see benefits of read and write
request being sent do the disk in parallel.
+smbclient reparse point symlink parameters reversed
+===================================================
+
+A bug in smbclient caused the 'symlink' command to reverse the
+meaning of the new name and link target parameters when creating a
+reparse point symlink against a Windows server. As this is a
+little used feature the ordering of these parameters has been
+reversed to match the parameter ordering of the UNIX extensions
+'symlink' command. The usage message for this command has also
+been improved to remove confusion.
+
KNOWN ISSUES
============