summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2007-01-09 00:59:11 +0000
committerRoger Dingledine <arma@torproject.org>2007-01-09 00:59:11 +0000
commitabaf2231528aeaf9a5adfddee3971c3bbd238d7b (patch)
tree47a0cfceea852d18f86df75c5cabda2581c02b1d
parent254005fc1b17fd23dc75f031addcfa31e1c8bf57 (diff)
downloadtor-abaf2231528aeaf9a5adfddee3971c3bbd238d7b.tar.gz
tor-abaf2231528aeaf9a5adfddee3971c3bbd238d7b.zip
catch nick's attempt at revisionist history
svn:r9308
-rw-r--r--ChangeLog6
1 files changed, 3 insertions, 3 deletions
diff --git a/ChangeLog b/ChangeLog
index 85bf8b48e6..ff034fa577 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -45,6 +45,9 @@ Changes in version 0.1.2.6-alpha - 2007-??-??
BandwidthRate was over to 2 GB.
- Warn that using select() on any libevent version before 1.1 will be
unnecessarily slow (even for select()).
+ - Flush ERR-level status events just like we currently flush ERR-level
+ log events, so that a Tor shutdown doesn't prevent the controller from
+ learning about current events.
Changes in version 0.1.2.5-alpha - 2007-01-06
@@ -208,9 +211,6 @@ Changes in version 0.1.2.5-alpha - 2007-01-06
when the last second's write or read exceeds the allotted bandwidth.
- Report "unrecognized key" rather than an empty string when the
controller tries to fetch a networkstatus that doesn't exist.
- - Flush ERR-level status events just like we currently flush ERR-level
- log events, so that a Tor shutdown doesn't prevent the controller from
- learning about current events.
Changes in version 0.1.2.4-alpha - 2006-12-03