[or-cvs] clean up rc1 changelog

[arma@xxxxxxxx (Roger Dingledine)]

Update of /home2/or/cvsroot/tor
In directory moria.mit.edu:/home2/arma/work/onion/cvs/tor

Modified Files:
	ChangeLog 
Log Message:
clean up rc1 changelog


Index: ChangeLog
===================================================================
RCS file: /home2/or/cvsroot/tor/ChangeLog,v
retrieving revision 1.72
retrieving revision 1.73
diff -u -d -r1.72 -r1.73
--- ChangeLog	28 Mar 2005 04:14:22 -0000	1.72
+++ ChangeLog	29 Mar 2005 02:44:24 -0000	1.73
@@ -22,7 +22,7 @@
       required exit node for certain sites.
     - Add a new TrackHostExits config directive to trigger addressmaps
       for certain incoming socks addresses -- for sites that break when
-      your exit keeps changing.
+      your exit keeps changing (based on patch from Mike Perry).
     - Redo the client-side dns cache so it's just an addressmap too.
     - Notice when our IP changes, and reset stats/uptime/reachability.
     - When an application is using socks5, give him the whole variety of
@@ -31,11 +31,11 @@
     - A more sane version numbering system. See
       http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
     - New contributed script "exitlist": a simple python script to
-      parse directories and find tor nodes that exit to listed
-      nodes/ports.
+      parse directories and find Tor nodes that exit to listed
+      addresses/ports.
     - New contributed script "privoxy-tor-toggle" to toggle whether
-      privoxy uses tor. Seems to be configured for debian by default.
-    - Report HTTP reasons to when getting a response from directory
+      Privoxy uses Tor. Seems to be configured for Debian by default.
+    - Report HTTP reasons to client when getting a response from directory
       servers -- so you can actually know what went wrong.
     - New config option MaxAdvertisedBandwidth which lets you advertise
       a low bandwidthrate (to not attract as many circuits) while still
@@ -58,8 +58,6 @@
         not just the last one, will have a minimum uptime.
       - New config option LongLivedPorts to indicate application streams
         that will want high uptime circuits.
-      - When attaching a stream to a circuit, pay attention to its
-        requirements.
       - Servers reset uptime when a dir fetch entirely fails. This
         hopefully reflects stability of the server's network connectivity.
       - If somebody starts his tor server in Jan 2004 and then fixes his
@@ -71,8 +69,8 @@
       and connect streams can use internal circs if they want.
     - New circuit pooling algorithm: make sure to have enough circs around
       to satisfy any predicted ports, and also make sure to have 2 internal
-      circs around if we've required internal circs lately (with high
-      uptime if we've seen that lately).
+      circs around if we've required internal circs lately (and with high
+      uptime if we've seen that lately too).
     - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
       which describes how often we retry making new circuits if current
       ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
@@ -105,8 +103,8 @@
       for google.com" problem.
     - Make "platform" string in descriptor more accurate for Win32 servers,
       so it's not just "unknown platform".
-    - Fix an edge case in parsing config options (thanks weasel)
-      if they say "--" on the commandline, it's not an option
+    - Fix an edge case in parsing config options (thanks weasel).
+      If they say "--" on the commandline, it's not an option.
     - Reject odd-looking addresses at the client (e.g. addresses that
       contain a colon), rather than having the server drop them because
       they're malformed.
@@ -115,7 +113,7 @@
     - REUSEADDR on normal platforms means you can rebind to the port
       right after somebody else has let it go. But REUSEADDR on win32
       means to let you bind to the port _even when somebody else
-      already has it bound_. So, don't do that on Win32.
+      already has it bound_! So, don't do that on Win32.
     - Change version parsing logic: a version is "obsolete" if it is not
       recommended and (1) there is a newer recommended version in the
       same series, or (2) there are no recommended versions in the same
@@ -126,7 +124,7 @@
       the socks reject.
 
   o Helpful fixes:
-    - Require BandwidthRate to be at least 20kB/s for servers
+    - Require BandwidthRate to be at least 20kB/s for servers.
     - When a dirserver causes you to give a warn, mention which dirserver
       it was.
     - New config option DirAllowPrivateAddresses for authdirservers.
@@ -143,12 +141,12 @@
     - If we get an incredibly skewed timestamp from a dirserver mirror
       that isn't a verified OR, don't warn -- it's probably him that's
       wrong.
-    - Since we ship our own privoxy on os x, tweak it so it doesn't write
+    - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
       cookies to disk and doesn't log each web request to disk. (Thanks
       to Brett Carrington for pointing this out.)
     - When a client asks us for a dir mirror and we don't have one,
       launch an attempt to get a fresh one.
-    - If we're hibernating and we get a sigint, exit immediately.
+    - If we're hibernating and we get a SIGINT, exit immediately.
     - Add --with-dmalloc ./configure option, to track memory leaks.
     - And try to free all memory on closing, so we can detect what
       we're leaking.