#
#
# patch "NEWS"
#  from [b1f1b755c9eead289ac37fd03a3f483381475d9d]
#    to [7d18669ce20c3783dfbf9562659f126d95ad42cc]
#
============================================================
--- NEWS	b1f1b755c9eead289ac37fd03a3f483381475d9d
+++ NEWS	7d18669ce20c3783dfbf9562659f126d95ad42cc
@@ -18,25 +18,29 @@ xxx xxx xx xx:xx:xx UTC 2009
         - C++ exceptions in Lua extension functions are now converted into
           Lua errors catchable with pcall, instead of causing a crash.
 
-        - Updating a locally-modified file no longer clobbers file system
-	  properties (such as the execute bit) as long as those properties
-	  correspond to versioned attributes on the file (such as
-	  mtn:execute).  Monotone now also informs the user when execute
-	  permissions are changed.
+        - In 0.43 revert became excessively noisy and would report changes to
+          all attributes on included files and directories regardless of whether
+          the attributes had been changed or not. This has been silenced.
+          Monotone will now specifically report changes to execute permissions
+          only when they occur.
 
+        - In 0.43 monotone would lose execute permissions on all files modified
+          during an update operation. Execute permissions are now reset on
+          updated files that have the mtn:execute attribute set to true.
+
         - Invalid revision selectors now cause an immediate error instead of
-	  being dropped from the selection.  The old behavior could produce
-	  undesired effects from typoed commands, such as spewing a list of
-	  all revisions in the database.
+          being dropped from the selection.  The old behavior could produce
+          undesired effects from typoed commands, such as spewing a list of
+          all revisions in the database.
 
-	- If "automate stdio" is in use, invalid selectors are reported via
+        - If "automate stdio" is in use, invalid selectors are reported via
           the automate protocol rather than on stderr.
 
         - "Best-effort" character set conversions now work again; 'mtn log'
-	  will not crash just because there is a change log entry with a
-	  character not representable in your locale.  However, if your system
-	  iconv(3) implementation does not support the //TRANSLIT extension,
-	  you may see garbage characters in the above scenario.
+          will not crash just because there is a change log entry with a
+          character not representable in your locale.  However, if your system
+          iconv(3) implementation does not support the //TRANSLIT extension,
+          you may see garbage characters in the above scenario.
 
         Internal