s3:WHATSNEW.txt: remove the "strict allocate" default value

commit dc36d75d5fddaa351025e8eb8140f401b66aeb9d
reverted the change to true, because it makes Samba
unusable on systems without Linux and a modern Filesystem.

metze

Autobuild-User: Stefan Metzmacher <metze@samba.org>
Autobuild-Date: Wed Apr 13 21:21:10 CEST 2011 on sn-devel-104
(cherry picked from commit 8acc57d6a26297d1430be0d73ce4dfbeba9a8b1c)
(cherry picked from commit 0ec0aa8ee51742fa55714ce4efb09caa430bec90)

diff --git a/WHATSNEW.txt b/WHATSNEW.txt
index a5cdecab0ca43e3d791c8db7130b560e6d54e63e..cea21ae043dea784ead9a9af05f27c84d07c2c4d 100644 (file)
--- a/WHATSNEW.txt
+++ b/WHATSNEW.txt
@@ -225,7 +225,6 @@ smb.conf changes
    smb2 max read                      New             1048576
    smb2 max trans                     New             1048576
    smb2 max write                     New             1048576
-   strict allocate                    Changed Default Yes
    username map cache time            New             0
    winbind max clients                New             200