branches/zip:

White space and formatting cleanup in the ChangeLog

ChangeLog

@@ -4,9 +4,9 @@
 	Make the test pass with zlib 1.2.3.3. Apparently, the definition
 	of compressBound() has changed between zlib versions, and the
 	maximum record size of a table with 1K compressed page size has
-	been reduced by one byte.  This is an arbitrary test.  In
-	practical applications, for good write performance, the compressed
-	page size should be chosen to be bigger than the absolute minimum.
+	been reduced by one byte. This is an arbitrary test. In practical
+	applications, for good write performance, the compressed page size
+	should be chosen to be bigger than the absolute minimum.
 
 2009-09-16	The InnoDB Team
 
@@ -50,9 +50,9 @@
 
 2009-08-27	The InnoDB Team
 
-	* buf/buf0buf.c, buf/buf0lru.c, buf/buf0rea.c,
-	handler/ha_innodb.cc, include/buf0buf.h, include/buf0buf.ic,
-	include/buf0lru.h, include/ut0ut.h, ut/ut0ut.c:
+	* buf/buf0buf.c, buf/buf0lru.c, buf/buf0rea.c, handler/ha_innodb.cc,
+	include/buf0buf.h, include/buf0buf.ic, include/buf0lru.h,
+	include/ut0ut.h, ut/ut0ut.c:
 	Make it possible to tune the buffer pool LRU eviction policy to be
 	more resistant against index scans. Introduce the settable global
 	variables innodb_old_blocks_pct and innodb_old_blocks_time for
@@ -64,10 +64,10 @@
 	innodb_old_blocks_time milliseconds ago (default 0, meaning every
 	block). The idea is that in index scans, blocks will be accessed
 	a few times within innodb_old_blocks_time, and they will remain in
-	the "old" section of the LRU list.  Thus, when
-	innodb_old_blocks_time is nonzero, blocks retrieved for one-time
-	index scans will be more likely candidates for eviction than
-	blocks that are accessed in random patterns.
+	the "old" section of the LRU list. Thus, when innodb_old_blocks_time
+	is nonzero, blocks retrieved for one-time index scans will be more
+	likely candidates for eviction than blocks that are accessed in
+	random patterns.
 
 2009-08-26	The InnoDB Team