[master] fd39f38 Whitespace OCD

Federico G. Schwindt fgsch at lodoss.net
Fri Mar 4 14:20:37 CET 2016


commit fd39f38ee6c63b5a5a98cdbbb2edb82f1470c0c6
Author: Federico G. Schwindt <fgsch at lodoss.net>
Date:   Fri Mar 4 08:27:07 2016 +0000

    Whitespace OCD

diff --git a/doc/sphinx/phk/firstdesign.rst b/doc/sphinx/phk/firstdesign.rst
index 216101a..32f27b2 100644
--- a/doc/sphinx/phk/firstdesign.rst
+++ b/doc/sphinx/phk/firstdesign.rst
@@ -178,7 +178,7 @@ where we kept thinking in the old frame of reference (ie: Squid)::
 		How long time after the expiry can we serve a cached copy
 		of this document while we have reason to belive the backend
 		can supply us with an update ?
-		
+
 		How long time after the expiry can we serve a cached copy
 		of this document if the backend does not reply or is
 		unreachable.
@@ -521,7 +521,7 @@ Soon those two inspiratons collided::
 		statements:	/* empty */
 				| statement
 				| statements statement
-				
+
 
 		statement:	if_statement
 				| call_statement
@@ -641,7 +641,7 @@ Soon those two inspiratons collided::
 			if (obj.size > 256k) {
 				no-cache
 			} else if (obj.size > 32k && obj.ttl < 2m) {
-				obj.tll = 5m				
+				obj.tll = 5m
 			}
 			if (backend.response_time > 2.0s) {
 				set ttl *= 2.0
@@ -682,7 +682,7 @@ Soon those two inspiratons collided::
 	object on the generation list, the purge object has been completed
 	and will be removed.  A log entry is written with number of compares
 	and number of hits.
-		
+
 	-----------------------------------------------------------------------
 	Random notes
 
@@ -836,7 +836,7 @@ Soon those two inspiratons collided::
 			Logfile processor
 			-i shmemfile
 			-e regexp
-			-o "/var/log/varnish.%Y%m%d.traffic" 
+			-o "/var/log/varnish.%Y%m%d.traffic"
 			-e regexp2
 			-n "/var/log/varnish.%Y%m%d.exception"  (NCSA format)
 			-e regexp3
@@ -1063,7 +1063,7 @@ A couple of days later the ideas had gel'ed::
 			if (obj.size > 256k) {
 				no-cache
 			} else if (obj.size > 32k && obj.ttl < 2m) {
-				obj.tll = 5m				
+				obj.tll = 5m
 			}
 			if (backend.response_time > 2.0s) {
 				set ttl *= 2.0
@@ -1104,7 +1104,7 @@ A couple of days later the ideas had gel'ed::
 	object on the generation list, the purge object has been completed
 	and will be removed.  A log entry is written with number of compares
 	and number of hits.
-		
+
 	-----------------------------------------------------------------------
 	Random notes
 
@@ -1258,7 +1258,7 @@ A couple of days later the ideas had gel'ed::
 			Logfile processor
 			-i shmemfile
 			-e regexp
-			-o "/var/log/varnish.%Y%m%d.traffic" 
+			-o "/var/log/varnish.%Y%m%d.traffic"
 			-e regexp2
 			-n "/var/log/varnish.%Y%m%d.exception"  (NCSA format)
 			-e regexp3
diff --git a/doc/sphinx/phk/thatslow.rst b/doc/sphinx/phk/thatslow.rst
index c8c905a..7bfd76a 100644
--- a/doc/sphinx/phk/thatslow.rst
+++ b/doc/sphinx/phk/thatslow.rst
@@ -101,7 +101,7 @@ observation::
 And eventually I no longer think about code lines as an asset
 to be accumulated, but rather as an expenditure to be avoided.
 
-When I started Varnish, one of my main personal goals was to 
+When I started Varnish, one of my main personal goals was to
 make it my highest quality program - ever [#f4]_.
 
 This is why Varnish is written in "pidgin C" style and lousy with



More information about the varnish-commit mailing list