[tor-commits] [tor/release-0.4.6] Small edits to changelog

[dgoulet at torproject.org]

commit d4253bbea02ba7da20308ea93d0666cca647930e
Author: Nick Mathewson <nickm at torproject.org>
Date:   Mon Jan 11 12:55:28 2021 -0500

    Small edits to changelog
---
 ChangeLog | 45 +++++++++++++++++++++------------------------
 1 file changed, 21 insertions(+), 24 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index e883b8b6af..961ac14eba 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -9,49 +9,46 @@ Changes in version 0.4.5.3-rc - 2021-01-12
   before 0.4.5.x is stable.
 
   o Minor features (crypto):
-    - Fix undefined behavior on our Keccak library. The bug only appears
-      on platforms with 32-byte CPU cache lines (e.g. armv5tel) and
-      would result in wrong digests. Fixes bug 40210; bugfix on
+    - Fix undefined behavior on our Keccak library. The bug only
+      appeared on platforms with 32-byte CPU cache lines (e.g. armv5tel)
+      and would result in wrong digests. Fixes bug 40210; bugfix on
       0.2.8.1-alpha. Thanks to Bernhard Ãœbelacker, Arnd Bergmann and
       weasel for diagnosing this.
 
   o Minor features (documentation):
-    - Mention the !badexit directive that can appear in an authority's
-      approved-routers file, and update the description of the !invalid
-      directive. Closes ticket 40188.
+    - Mention that the "!badexit" directive that can appear in an
+      authority's approved-routers file, and update the description of
+      the "!invalid" directive. Closes ticket 40188.
 
   o Minor bugfixes (build):
-    - Fix the --enable-static-tor switch to properly set the -static
+    - Fix the "--enable-static-tor" switch to properly set the "-static"
       compile option onto the tor binary only. Fixes bug 40111; bugfix
       on 0.2.3.1-alpha.
-    - Path to static libevent has been fixed as well which affects the
-      --enable-static-libevent to behave correctly now. The .a file is
-      in .libs/ of libevent repository, not at the root.
 
   o Minor bugfixes (config, bridge):
     - Really fix the case where torrc has a missing ClientTransportPlugin
       but configured with a Bridge line and UseBridges. Previously, we
-      failed to also look at the managed proxy list and thus it would
-      fail for the "exec" case. Fixes bug 40106; bugfix on 0.4.5.1-alpha.
+      didn't look at the managed proxy list and thus would fail for the
+      "exec" case. Fixes bug 40106; bugfix on 0.4.5.1-alpha.
 
   o Minor bugfixes (logging, relay):
-    - Logs the address discovered by the directory authorities if none
-      were configured or detected before. Fixes bug 40201; bugfix
-      on 0.4.5.1-alpha.
-    - When launching bandwidth testing circuit, don't log notice that we
-      are doing a reachability test. Furthermore, avoid to trigger a
-      "CHECKING_REACHABILITY" control event. Fixes bug 40205; bugfix
+    - Log our address as reported by the directory authorities, if none
+      was configured or detected before. Fixes bug 40201; bugfix
       on 0.4.5.1-alpha.
+    - When a launching bandwidth testing circuit, don't incorrectly call
+      it a reachability test, or trigger a "CHECKING_REACHABILITY"
+      control event. Fixes bug 40205; bugfix on 0.4.5.1-alpha.
 
   o Minor bugfixes (relay, statistics):
-    - The connection statistics were wrongly exported in the extrainfo
-      document due to a problem in the file loading function which would
-      wrongly truncate the file reporting the wrong information. It is
-      now fixed. Fixes bug 40226; bugfix on 0.4.5.1-alpha.
+    - Report the correct connection statistics in our extrainfo
+      documents. Previously there was a problem in the file loading
+      function which would wrongly truncate a state file, causing the
+      wrong information to be reported. Fixes bug 40226; bugfix
+      on 0.4.5.1-alpha.
 
   o Minor bugfixes (SOCKS5):
-    - Handle partial socks5 messages correctly. Previously, our code
-      would send an incorrect error message if it got a socks5 request
+    - Handle partial SOCKS5 messages correctly. Previously, our code
+      would send an incorrect error message if it got a SOCKS5 request
       that wasn't complete. Fixes bug 40190; bugfix on 0.3.5.1-alpha.