X-Git-Url: https://wimlib.net/git/?p=wimlib;a=blobdiff_plain;f=NEWS;h=0917d65e893ce78bd27b730172d42ac264826f86;hp=55235ead2f5ba9096c4d0ae64c7ac452a72a5f24;hb=537e20bd131824aef656de162919682fcb92bd7d;hpb=eb323afc439593fbc8701632cd5d154d5ec59a54

diff --git a/NEWS b/NEWS
index 55235ead..0917d65e 100644
--- a/NEWS
+++ b/NEWS
@@ -1,7 +1,33 @@
-Version 1.8.1-BETA:
+Version 1.8.2-BETA:
+	This release contains various minor bug fixes and improvements,
+	including:
+
+		Reduced the stack space used by directory tree scans.
+
+		Fixed a bug where on 32-bit systems, the library could enter an
+		infinite loop if a WIM file was malformed in a specific way.
+
+		Windows symbolic links and junctions in mounted WIM images are
+		now automatically rewritten to be valid in the mounted location.
+
+		Reparse point fixes: correctly handle the "ReparseReserved"
+		field, and correctly handle "empty" (data-less) reparse points.
+
+		Improved validation of filenames.
+
+		Fixed the test scripts to work in a Turkish locale.
+
+		Fixed handling of EINTR during data I/O.
+
+		Optimized memory usage of some data structures.
+
+Version 1.8.1:
 	Fixed a bug in the LZX decompressor: malicious input data could cause
 	out of bounds writes to memory (since wimlib v1.2.2).
 
+	The output of the 'wiminfo' command now consolidates various boolean
+	flags (such as "Relative path junction") into a single line.
+
 	A file can now have both an unnamed data stream ("file contents") and a
 	reparse point stream.  Such files can exist as a result of the use of
 	certain Windows features, such as offline storage, including "OneDrive".
@@ -14,6 +40,9 @@ Version 1.8.1-BETA:
 	On Windows, named data streams are now correctly extracted to existing
 	"readonly" directories.  Before, an error would be reported.
 
+	On Windows, it is now possible to do a "WIMBoot mode" extraction with
+	non-standalone WIMs such as delta WIMs.
+
 	On Windows, when doing an extraction in "WIMBoot mode", files larger
 	than 4 gigabytes are now never extracted as externally backed.  This
 	works around a bug in Microsoft's "WOF" driver.