bk commit - mysqldoc tree (guilhem:1.2748)

[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.2748 05/03/21 14:39:54 guilhem@stripped +1 -0
  A posteriori discovering that bugfix missed the release by 2 days, correcting changelog :(

  Docs/manual.texi
    1.2583 05/03/21 14:39:41 guilhem@stripped +6 -6
    A posteriori discovering that bugfix missed the release by 2 days, correcting changelog :(

# 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.2582/Docs/manual.texi	2005-03-21 08:12:42 +01:00
+++ 1.2583/Docs/manual.texi	2005-03-21 14:39:41 +01:00
@@ -98877,6 +98877,12 @@
 @item
 Fixed a bug that caused the slave to stop on statements that produced
 an error on the master. (Bug #8412)
+@item
+If multiple semicolon-separated statements were received in a single packet,
+they were written to the binary log as a single event rather than as
+separate per-statement events. For a server serving as a replication master,
+this caused replication to fail when the event was sent to slave servers.
+(Bug #8436)
 @end itemize
 
 @node News-4.1.10, News-4.1.9, News-4.1.11, News-4.1.x
@@ -98990,12 +98996,6 @@
 corrupted when a non-4.1 client was served a result originally generated for a
 4.1 client. The query cache was not keeping track of which client/server
 protocol was being used. (Bug #6511)
-@item
-If multiple semicolon-separated statements were received in a single packet,
-they were written to the binary log as a single event rather than as
-separate per-statement events. For a server serving as a replication master,
-this caused replication to fail when the event was sent to slave servers.
-(Bug #8436)
 @item
 Fixed @code{LOAD INDEX} statement to actually load index in memory. (Bug #8452)
 @item