Handle API failure during resend
    API failure could cause release of table object, which will make resend crash
      when dereferencing table object
      
    Solution, use table_id+hash+schemaversion instead of *raw* pointer in resend

  Make sure not to handle API_FAILREQ if it's already handled

  Make sure head after undo execute does not point to last page of file
  As this will confuse next write to group

  merge to 5.1, adopt testprg to optimized node recovery

into  perch.ndb.mysql.com:/home/jonas/src/51-telco-gca

  Handle random(not in order) LQHKEYREQ failures during node-restart

into  poseidon.mysql.com:/home/tomas/mysql-5.1-telco-gca

added error code for failing send signal and timeout waiting for node failure

Bug #26997  	mysqld segfault when in single user mode

into  perch.ndb.mysql.com:/home/jonas/src/tmp/mysql-5.1-telco-gca

Bug #25275 SINGLE USER MODE prevents ALTER on non-ndb tables for other mysqld nodes
- correction of part 1
    add ndb_waiter option to wait for single user mode

BUG#25743 If undo_buffer_size (for LG) greater than the inital shared memory (default 20M), ndbd nodes are crashed

into  poseidon.mysql.com:/home/tomas/mysql-5.1-telco-gca

into  poseidon.mysql.com:/home/tomas/mysql-5.1-telco-gca

  fix printout
  crashes testSystemRestart -n SR_UNDO

  fix printout
  crashes testSystemRestart -n SR_UNDO

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

into  poseidon.mysql.com:/home/tomas/mysql-5.1-telco-gca

(part 1)
- add signal data
- add ref in dict on create/drop table/index

- terminate printing

- only creat systable if conencted to ndb

into  poseidon.mysql.com:/home/tomas/mysql-5.1-telco-gca

ndb - 5.1.16 uint64 align for ndb_restore
(backport)

into  poseidon.mysql.com:/home/tomas/mysql-5.1-telco-gca

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

  Make sure GCP_SAVEREQ is not allowed before START_RECCONF has been sent...START_RECREQ is not enough

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

  Make StartREDO come up as default in cluster log

  make sure logPartPtr is correctly initialized

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

  fix overflow that could occur when have either lots of dd-data or very high dd-parallelism

  fix bug in extent/page allocation when *using* >1gb datafiles

  write testcase for bug#26450...
  no solution however...

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

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