bk commit into 5.1 tree (jonas:1.2133)

[jonas]

Below is the list of changes that have just been committed into a local
5.1 repository of jonas. When jonas 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://dev.mysql.com/doc/mysql/en/installing-source-tree.html

ChangeSet@stripped, 2007-04-13 07:18:41+02:00, jonas@stripped +2 -0
  drop6p7

  cluster_change_hist.txt@stripped, 2007-04-13 07:18:39+02:00, jonas@stripped +13 -0
    update cluster change hist

  configure.in@stripped, 2007-04-13 07:18:40+02:00, jonas@stripped +2 -2
    update configure.in

# 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:	jonas
# Host:	perch.ndb.mysql.com
# Root:	/home/jonas/src/drop6

--- 1.335/configure.in	2007-04-13 07:18:44 +02:00
+++ 1.336/configure.in	2007-04-13 07:18:44 +02:00
@@ -7,7 +7,7 @@
 AC_CANONICAL_SYSTEM
 # The Docs Makefile.am parses this line!
 # Don't forget to also update the NDB lines below.
-AM_INIT_AUTOMAKE(mysql, 5.2.1-a_drop6p6)
+AM_INIT_AUTOMAKE(mysql, 5.2.1-a_drop6p7)
 AM_CONFIG_HEADER(config.h)
 
 PROTOCOL_VERSION=10
@@ -19,7 +19,7 @@
 NDB_VERSION_MAJOR=5
 NDB_VERSION_MINOR=2
 NDB_VERSION_BUILD=1
-NDB_VERSION_STATUS="a_drop6p6"
+NDB_VERSION_STATUS="a_drop6p7"
 
 # Set all version vars based on $VERSION. How do we do this more elegant ?
 # Remember that regexps needs to quote [ and ] since this is run through m4

--- 1.26/cluster_change_hist.txt	2007-04-13 07:18:44 +02:00
+++ 1.27/cluster_change_hist.txt	2007-04-13 07:18:44 +02:00
@@ -9,6 +9,19 @@
 (note that this does not apply to the not yet released Alcatel features for Partitioning and Replication)
 (* == Alcatel has hit this bug)
 
+-------------------------------
+
+Alcatel Drop 6p7 (Fri 13 April 2007)
+
+    * Bug#27434 Incorrect handling of FragState in take-over during SR csc#13995 csc#15677
+      Bug#27466 nf during nr can leave cluster in inconsistent state
+      Bug#27651 Very high load can cause event api to get out of sync, "out of order buckets" 
+    * Bug#27663 Missmatched free/delete in listObjects csc#15722 
+    * Bug#27728 Partially connected API's can cause problem for SUMA csc#14882 
+    * Bug#27748 Inconsistent replication(backup) with some multi-update combinations csc#15842
+      Bug#27529 Slave crashes on lots of updates 
+
+-------------------------------
 
 Alcatel Drop 6p6 (Thu 22 March 2007)