From: Date: August 12 2005 5:23am
Subject: bk commit - mysqldoc@docsrva tree (jan:1.3242)
List-Archive: http://lists.mysql.com/internals/28206
Message-Id: <200508120323.j7C3NKXV020468@hundin.mysql.fi>

Below is the list of changes that have just been committed into a local
mysqldoc repository of jan. When jan does a push these changes will
be propagated to the main repository and, within 24 hours after the
push, to the public repository.
For information on how to access the public repository
see http://www.mysql.com/doc/I/n/Installing_source_tree.html

ChangeSet
  1.3242 05/08/12 06:23:18 jan@stripped +1 -0
  Merge bk://mysqldoc@stripped
  into  hundin.mysql.fi:/home/jan/mysqldoc

  refman/innodb.xml
    1.21 05/08/12 06:23:15 jan@stripped +0 -0
    Auto merged

# This is a BitKeeper patch.  What follows are the unified diffs for the
# set of deltas contained in the patch.  The rest of the patch, the part
# that BitKeeper cares about, is below these diffs.
# User:	jan
# Host:	hundin.mysql.fi
# Root:	/home/jan/mysqldoc/RESYNC

--- 1.20/refman/innodb.xml	2005-08-11 15:23:13 +03:00
+++ 1.21/refman/innodb.xml	2005-08-12 06:23:15 +03:00
@@ -1000,8 +1000,8 @@
           outage can erase the last second of transactions. However,
           InnoDB's crash recovery is not affected and thus crash
           recovery does work regardless of the value. Note that many
-          operating systems and some disk hardware fool in the
-          flush-to-disk operation. They may tell to
+          operating systems and some disk hardware fail in the
+          flush-to-disk operation. They may tell
           <command>mysqld</command> that the flush has taken place,
           though it has not. Then the durability of transactions is not
           guaranteed even with the setting 1, and in the worst case a