[minion-cvs] Normalize whitespace

[nickm@seul.org (Nick Mathewson)]

Update of /home/minion/cvsroot/src/minion
In directory moria.mit.edu:/tmp/cvs-serv27991

Modified Files:
	HACKING MANIFEST.in Makefile README 
Log Message:
Normalize whitespace

Index: HACKING
===================================================================
RCS file: /home/minion/cvsroot/src/minion/HACKING,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -d -r1.15 -r1.16
--- HACKING	16 Jan 2003 05:57:01 -0000	1.15
+++ HACKING	20 Feb 2003 16:57:37 -0000	1.16
@@ -8,7 +8,7 @@
 
         A working /dev/urandom (see PORTING NOTES below)
 
-THINGS TO HACK:  (Good introductory projects that I won't get to myself for 
+THINGS TO HACK:  (Good introductory projects that I won't get to myself for
   at least a version or two.)
 
 - We need a windows port!  (A client-only port would be a good start.)  Most
@@ -86,7 +86,7 @@
   parallel with the processing code, but the processing thread accounts (I
   think) for most of the CPU use.  It would be nice to support multiple
   processing threads and multiple network threads (round-robin, not
-  one-per-connection). (Difficulty: easy/moderate, depending on your 
+  one-per-connection). (Difficulty: easy/moderate, depending on your
   knowledge of writing multithreaded code. Invasiveness: slight.)
 
 THINGS TO THINK ABOUT AND HACK: (Introductory projects that will take some
@@ -126,7 +126,7 @@
   an IPv4-only server simply cannot deliver to a server without an IPv4
   address.  Any path-generation algorithm I can come up with has troublesome
   anonymity implications.  If you can come up with an algorithm that
-  doesn't, the code should be pretty easy to do.  (Spec difficulty: ????. 
+  doesn't, the code should be pretty easy to do.  (Spec difficulty: ????.
   Implementation difficulty: easy.  Invasiveness: some.)
 
 NON-HACKING PROJECTS:

Index: MANIFEST.in
===================================================================
RCS file: /home/minion/cvsroot/src/minion/MANIFEST.in,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -d -r1.6 -r1.7
--- MANIFEST.in	5 Jan 2003 04:56:51 -0000	1.6
+++ MANIFEST.in	20 Feb 2003 16:57:38 -0000	1.7
@@ -3,6 +3,3 @@
 include etc/mixminiond.conf etc/blacklist.conf
 # Old versions of distutils miss header files
 include src/_minionlib.h
-
-
-

Index: Makefile
===================================================================
RCS file: /home/minion/cvsroot/src/minion/Makefile,v
retrieving revision 1.39
retrieving revision 1.40
diff -u -d -r1.39 -r1.40
--- Makefile	20 Feb 2003 02:27:39 -0000	1.39
+++ Makefile	20 Feb 2003 16:57:38 -0000	1.40
@@ -246,7 +246,7 @@
 	   | xargs -0 grep 'XXXX00[123]\|FFFF00[123]\|DOCDOC\|????00[123]'
 
 eolspace:
-	perl -i.bak -pe 's/\s*\n$$/\n/;' ACKS HACKING LICENSE MANIFEST.in \
+	perl -i.bak -pe 's/(\S)\s*\n$$/\1\n/;' ACKS HACKING LICENSE MANIFEST.in \
 		Makefile README TODO pycheckrc setup.py src/*.[ch] \
 		lib/mixminion/*.py lib/mixminion/*/*.py
 

Index: README
===================================================================
RCS file: /home/minion/cvsroot/src/minion/README,v
retrieving revision 1.36
retrieving revision 1.37
diff -u -d -r1.36 -r1.37
--- README	20 Feb 2003 06:38:27 -0000	1.36
+++ README	20 Feb 2003 16:57:38 -0000	1.37
@@ -67,7 +67,7 @@
       - mixminion stop-server and mixminion reload-server commands.
 
 NEW IN VERSION 0.0.3rc1:
-   CLIENT:   
+   CLIENT:
       - Single-use reply blocks (SURBs) are fully supported and available.
       - You can use client-side pooling: it holds messages until you're
         ready to send them.  Pooling also prevents you from losing
@@ -86,7 +86,7 @@
         stalling under heavy loads.  Now the network should remain fairly
         responsive under far more traffic than before.
       - When a message delivery fails, the retry schedule is more reasonable.
-        By default, a server will retry an undeliverable message every 
+        By default, a server will retry an undeliverable message every
         30 minutes for a day, then every 7 hours for 5 days.
       - All modules that use SMTP now set a "X-Anonymous: yes" header.
    CONFORMANCE:
@@ -347,9 +347,9 @@
       If you specify a "SURBAddress" field in ~/.mixminionrc, you may
       omit the target address:
 
-      mixminion generate-surb 
+      mixminion generate-surb
 
-      Also, you can control path selection in the same way as with 
+      Also, you can control path selection in the same way as with
       sending messages:
 
       mixminion generate-surb -H 3        (a 3-hop path)
@@ -378,7 +378,7 @@
       mixminion send -R <reply-block-filename> -i <input-filename>
 
       The other options to 'send' and 'pool' still apply; the reply block
-      takes the place of the destination address: 
+      takes the place of the destination address:
          mixminion send -R <reply-block>          (Read from stdin)
          mixminion send -R <reply-block> -D yes   (Reload directory)
          mixminion send -R <reply-block> -H 4     (Use 4 hops before reply.)
@@ -391,7 +391,7 @@
       block to 2 users, it will only work for one of them, once.
 
       As a convenience, if you have a file containing many reply blocks,
-      you can use it with '-R': the client will choose the first reply 
+      you can use it with '-R': the client will choose the first reply
       block from the file which has not expired, and which you have not
       yet used.