bk commit - mysqldoc tree (guilhem:1.2725)

[guilhem]

Below is the list of changes that have just been committed into a local
mysqldoc repository of guilhem. When guilhem 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.2725 05/03/14 22:29:36 guilhem@stripped +1 -0
  moving changelog entry to the proper version (5.0.3) instead of 4.1.11 where the change
was not made.

  Docs/manual.texi
    1.2555 05/03/14 22:29:25 guilhem@stripped +6 -6
    moving changelog entry to the proper version (5.0.3) instead of 4.1.11 where the
change was not made.

# 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:	guilhem
# Host:	gbichot2.local
# Root:	/home/mysql_src/mysqldoc

--- 1.2554/Docs/manual.texi	2005-03-14 11:56:21 +01:00
+++ 1.2555/Docs/manual.texi	2005-03-14 22:29:25 +01:00
@@ -97338,6 +97338,12 @@
 an @code{InnoDB} deadlock or exceeded @code{innodb_lock_wait_timeout},
 it automatically retries @code{slave_transaction_retries} times before
 stopping with an error. The default is 10. (Bug #8325)
+@item
+When a client releases a user-level lock, @code{DO RELEASE_LOCK()} will not be
+written to the binary log anymore (this makes the binary log smaller); as a
+counterpart, the slave does not actually take the lock when it executes
+@code{GET_LOCK()}. This is mainly an optimization and should not affect
+existing setups. (Bug #7998)
 @end itemize
 
 Bugs fixed:
@@ -98358,12 +98364,6 @@
 stopping with an error. The default in MySQL 4.1 is 0. You must explicitly
 set the value greater than 0 to enable the ``retry'' behavior. (In MySQL
 5.0.3 or newer, the default is 10.) (Bug #8325)
-@item
-When a client releases a user-level lock, @code{DO RELEASE_LOCK()} will not be
-written to the binary log anymore (this makes the binary log smaller); as a
-counterpart, the slave does not actually take the lock when it executes
-@code{GET_LOCK()}. This is mainly an optimization and should not affect
-existing setups. (Bug #7998)
 @end itemize
 
 Bugs fixed: