into  april.(none):/home/svoj/devel/mysql/BUG17810/mysql-5.0

Write operations on tables created in 4.x with index on variable
length column results in index crash. Even REPAIR TABLE wasn't able
to fix broken index.

Problem was that packed key length size wasn't restored correctly.
In 5.0 packed key length size is either 1 or 2. In 4.x this length
is always 2, but is saved as 0.

This fix ensures that key length size is restored correctly for 4.x
tables.

into  poseidon.ndb.mysql.com:/home/tomas/mysql-5.0

into  mysql.com:/home/jimw/my/mysql-5.0-clean

into  poseidon.ndb.mysql.com:/home/tomas/mysql-5.0

into  mysql.com:/home/jimw/my/mysql-5.0-clean

into  mysql.com:/home/jimw/my/mysql-5.0-clean

into  mysql.com:/home/jimw/my/mysql-5.0-clean

into  mysql.com:/home/jimw/my/mysql-5.0-clean

  
  This patch simply adds sql_big_selects to the list of variables
  output by SHOW VARIABLES.

into  zim.(none):/home/brian/mysql/mysql-5.0

This patch restores sync_binlog.

- addded more retries to wait for nodefailure to complete
Bug #19039 multi node failure causes node failure handling not to complete
- patch to avoid this scenario when the management server is used to perform the stop
- wait for NF_COMPLETE_REP in management server before returning
ndb: allocate nodeid
- only retry on retryable error

- added retry handling of temporary transaction errors

into  poseidon.ndb.mysql.com:/home/tomas/mysql-5.0

into  perch.ndb.mysql.com:/home/jonas/src/mysql-5.0

into  perch.ndb.mysql.com:/home/jonas/src/mysql-5.0

into  mysql.com:/home/alexi/innodb/mysql-5.0-ss492

into  mysql.com:/home/alexi/innodb/mysql-5.0-ss492

into  mysql.com:/home/alexi/innodb/mysql-5.0-ss492

into  mysql.com:/home/alexi/innodb/mysql-5.0-ss492-work

  clone-off for 5.0.21

into  mysql.com:/home/alexi/innodb/mysql-5.0-ss492-work

 Use files innodb_mysql.[test|result] instead.

into sergbook.mysql.com:/usr/home/serg/Abk/mysql-5.0

 Fixed BUG#19217 "dict_load_indexes() may read the delete-mark incorrectly".

(reported by Stefano Di Paola)

into mysql.com:/home/psergey/mysql-5.0-bug15827-r2

too much memory. Instead, either create the equvalent SEL_TREE manually, or create only two ranges that
strictly include the area to scan
(Note: just to re-iterate: increasing NOT_IN_IGNORE_THRESHOLD will make optimization run slower for big 
IN-lists, but the server will not run out of memory. O(N^2) memory use has been eliminated)

small cleanup fixes in kernel/vm/Configuration