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

diff --git a/WHATSNEW.txt b/WHATSNEW.txt
index 4265627d7746b75b7438033516c3d835dafd9914..9a7547e4e29eeeb5ff7b64e6304625d7bd5d1f73 100644 (file)
--- 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
 ============