into  poseidon.mysql.com:/home/tomas/mysql-5.1-new-ndb

On some compiler/platform combination, an assignment of form *p= *p
would map to a memcpy() call, and Valgrind flags this as an overlapped
memcpy() error.

Fix by prefixing *p= *q with if(p!=q) when building for Valgrind
(HAVE_purify).

into  poseidon.mysql.com:/home/tomas/mysql-5.1-new-ndb

- add ndb_share connect_count to decide if share can be reused to setup replication

into  poseidon.mysql.com:/home/tomas/mysql-5.1-new-ndb

into  poseidon.mysql.com:/home/tomas/mysql-5.1-new-ndb

protect the setting of ndb_schema_share = NULL with a mutex

into  bk-internal.mysql.com:/data0/bk/mysql-5.1-arch

Just a bad copy/paste of help info

into  a88-113-38-195.elisa-laajakaista.fi:/home/my/bk/mysql-5.1

new behaviour is as follows:
1) node is refused to start, and should fail with message in error log that it must be restarted --initial
2) if cluster failure in this situation, node must also be restarted --intial
   if not SR will fail, with this message

into  eel.(none):/home/jonas/src/51-work

  fix failure during start

into  poseidon.mysql.com:/home/tomas/mysql-5.1-new-ndb

into  poseidon.mysql.com:/home/tomas/mysql-5.1-new-ndb

into  trift2.:/MySQL/M51/push-5.1

into  dev3-63.(none):/home/zhl/mysql/tree-merge/5.1/mysql-5.1-new-ndb

into  mysql.com:/home/gluh/MySQL/Merge/5.1-opt

into  dev3-63.(none):/home/zhl/mysql/tree-merge/5.1/mysql-5.1-new-ndb

additional call of file->extra() method with HA_EXTRA_NO_CACHE parameter

into  trift2.:/MySQL/M51/push-5.1

BUG#22025 Return correct error message when transporter error occured. Modify content of message structure of last patch.

into  rakia.gmz:/home/kgeorge/mysql/autopush/B23556-5.0-opt

  merge of the 5.0-opt tree

into  rakia.gmz:/home/kgeorge/mysql/autopush/B23556-5.0-opt

into  rakia.gmz:/home/kgeorge/mysql/autopush/B23556-5.1-opt

into  mysql.com:/windows/Linux_space/MySQL/mysql-5.1-new-ndb

into  rakia.gmz:/home/kgeorge/mysql/autopush/B25551-5.0-opt

into  mysql.com:/windows/Linux_space/MySQL/mysql-5.1

Bug #25522  Update with IN syntax Clustertable + Trigger leads to mysqld segfault: moved back assignment

into  mysql.com:/windows/Linux_space/MySQL/mysql-5.1-new-ndb

fix time period calculation

add the jamEntry()

Reworked a section of code that caused valgrind errors (and that partitioning was not happy about). 

The bug could cause choosing a sub-optimal execution plan for 
a single-table query if a unique index with many null keys were 
defined for the table. 
It happened because the code of the check_quick_keys function 
made an assumption that any key may occur in an unique index 
only once. Yet this is not true for keys with nulls that may 
have multiple occurrences in the index.

into  mysql.com:/windows/Linux_space/MySQL/mysql-5.1-new-ndb

into  mysql.com:/windows/Linux_space/MySQL/mysql-5.1

Bug #25522  Update with IN syntax Clustertable + Trigger leads to mysqld segfault: in start_stmt, only change query_state if starting a new transactions, in read_multi_range_next, change query state when end is reached