[or-cvs] More whitespace normalization

Wed Nov 10 01:20:20 UTC 2004

Update of /home/or/cvsroot/doc
In directory moria.mit.edu:/tmp/cvs-serv26659/doc

Modified Files:
	HACKING tor-spec.txt tor.1.in 
Log Message:
More whitespace normalization

Index: HACKING
===================================================================
RCS file: /home/or/cvsroot/doc/HACKING,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -d -r1.10 -r1.11

--- HACKING	9 May 2004 16:32:33 -0000	1.10
+++ HACKING	10 Nov 2004 01:20:17 -0000	1.11
@@ -53,14 +53,14 @@
      util.[ch] -- Miscellaneous portability and convenience functions.
 
   Files in ./src/or:
-  
+
    [General-purpose modules]
 
      or.h -- Common header file: include everything, define everything.
 
-     buffers.c -- Implements a generic buffer interface.  Buffers are 
+     buffers.c -- Implements a generic buffer interface.  Buffers are
         fairly opaque string holders that can read to or flush from:
-        memory, file descriptors, or TLS connections.  
+        memory, file descriptors, or TLS connections.
 
         Also implements parsing functions to read HTTP and SOCKS commands
         from buffers.
@@ -89,7 +89,7 @@
         results; clients use routers.c to parse them.
 
      dirserv.c -- Code to manage directory contents and generate
-        directories. [Directory server only] 
+        directories. [Directory server only]
 
      routers.c -- Code to parse directories and router descriptors; and to
         generate a router descriptor corresponding to this OR's
@@ -133,9 +133,9 @@
   All sockets in Tor are handled as different types of nonblocking
   'connections'.  (What the Tor spec calls a "Connection", the code refers
   to as a "Cell-speaking" or "OR" connection.)
-  
+
   Connections are implemented by the connection_t struct, defined in or.h.
-  Not every kind of connection uses all the fields in connection_t; see 
+  Not every kind of connection uses all the fields in connection_t; see
   the comments in or.h and the assertions in assert_connection_ok() for
   more information.
 
@@ -272,7 +272,7 @@
          command_process_cell -- Notices it is a relay cell, so calls:
           command_process_relay_cell -- Looks up the circuit for the cell,
                  makes sure the circuit is live, then passes the cell to:
-           circuit_deliver_relay_cell -- Passes the cell to each of: 
+           circuit_deliver_relay_cell -- Passes the cell to each of:
             relay_crypt -- Strips a layer of encryption from the cell and
                  notices that the cell is for local delivery.
             connection_edge_process_relay_cell -- extracts the cell's
@@ -317,7 +317,6 @@
                  back an acknowledgement (requesting that more cells be
                  sent to this stream).
 
-
 1.6. Routers, descriptors, and directories
 
    All Tor processes need to keep track of a list of onion routers, for
@@ -348,7 +347,7 @@
    directories.
 
 1.7. Data model
-  
+
   [XXX]
 
 1.8. Flow control
@@ -477,7 +476,6 @@
 
      [XXX insert references]
 
-
 # ======================================================================
 # Old HACKING document; merge into the above, move into tor-design.tex,
 # or delete.
@@ -574,7 +572,3 @@
 
   Currently the code tries for the primary router first, and if it's down,
   chooses the first available twin.
-
-
-
-

Index: tor-spec.txt
===================================================================
RCS file: /home/or/cvsroot/doc/tor-spec.txt,v
retrieving revision 1.67
retrieving revision 1.68
diff -u -d -r1.67 -r1.68
--- tor-spec.txt	27 Oct 2004 00:48:51 -0000	1.67
+++ tor-spec.txt	10 Nov 2004 01:20:17 -0000	1.68
@@ -563,7 +563,6 @@
    cells when both a) the window is <= 450, and b) there are less than
    ten cell payloads remaining to be flushed at that edge.
 
-
 7. Directories and routers
 
 7.1. Extensible information format
@@ -712,7 +711,7 @@
 
     "signed-directory"
 
-        Indicates the start of a 
+        Indicates the start of a
 
     "published" YYYY-MM-DD HH:MM:SS
 
@@ -756,7 +755,7 @@
         'verified' if its nickname AND digest match the one provided.
         [XXXX 'router-status' was added in 0.0.9pre5; older directory code
         uses 'running-routers' instead.]
- 
+
     "directory-signature" nickname-of-dirserver NL Signature
 
 Note:  The router descriptor for the directory server MUST appear first.

Index: tor.1.in
===================================================================
RCS file: /home/or/cvsroot/doc/tor.1.in,v
retrieving revision 1.33
retrieving revision 1.34
diff -u -d -r1.33 -r1.34
--- tor.1.in	10 Nov 2004 01:16:50 -0000	1.33
+++ tor.1.in	10 Nov 2004 01:20:17 -0000	1.34
@@ -95,7 +95,7 @@
 Every N seconds, Tor downloads a fresh directory, and re-uploads
 information about hidden services to the directory servers.  If
 running as a server, Tor also re-uploads information about itself to
-the directory servers.  (Tor also uploads this information whenever it 
+the directory servers.  (Tor also uploads this information whenever it
 changes.)  (Default: 600.)
 .TP
 \fBClientOnly \fR\fB0\fR|\fB1\fR\fP
@@ -217,7 +217,7 @@
 .TP
 \fBMyFamily \fR\fInickname,nickname,...\fP
 Declare that this Tor server is controlled or administered by a group
-or organization identical or similar to that of the other named servers.  
+or organization identical or similar to that of the other named servers.
 When two servers both declare that they are in the same 'family', Tor clients
 will not use them in the same circuit.
 .TP
@@ -296,7 +296,6 @@
 option is only useful for authoritative directories, so you probably
 don't want to use it.
 
-
 .SH HIDDEN SERVICE OPTIONS
 .PP
 The following options are used to configure a hidden service.

