on master node failure during qmgr-commitreq
    make sure to remove all committed failed nodes from failed/prepfailed arrays

  incorrect handling of commit/ignore error in unique index code

  add testcase

  make sure apicon timer is reset when setting CS_CONNECTED

  Fix correct log event on db-node disconnect

  This prevent any subsequent node restarts, but it's better than crashing an alive node

  Skip rollback if only committedRead in transaction

  add testcase for bug#24717
 + fix typo

  5.0 version
  Add some extra state to try to prevent sending committedread to node too early

  remove debug printouts

  Fix scan filter on bit types
  (note should probably be enabled in condition pushdown aswell)

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

m  ove mlock to much earlier in startphases
  not to affect heartbeats

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

  actually do run mlockall

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

  update error code list
  (for bug#24447)

  api disconnect just after SCAN_TABREQ

  Fix bug wrt to '\r' handling in latest commit to bug#24011

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

  Still leakage, make sure all unlinked operations are put back so they will be release
  (on failing blob operations, when AO_IgnoreError)

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

  Fix some too small buffers in backup
  

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

  Fixed a 4.1/5.0 vs. 5.1 name change in latest SR bug fix

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

  Fix monster SR bug making SR with ordered indexes (or temporary tables) broken

  this changes lock taken during peek, to decrease likelyhood of transaction abort
  

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

  Make sure postExecute is not run for blobs if AO_IgnoreError

  1) Handle not started nodes in dump 1000 (check for division by 0)
  2) Make sure to init variables in constructor

  note this does not happen in 5.0, but i'm committing it here to keep code same between 5.0 and 5.1

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

  Fix race-condition between COPY_GCIREQ (GCP) and lcpSetActiveStatusEnd
  Solution is _not_ to copy sysfileData from COPY_GCIREQ from "self"

  fix bug in test prg

  fix bug in handling of inactive timeout for scan, when all is delivered

  Add checking of REDO to earlier during SR
      so take-over of node can be performed
      if it can't be restarted using logs
      (which btw is really weird...as it _should_ be able to use logs of other node in node group)

  Otherwise cluster could be started and 1 fragment on one node could not have been restored
  Making the cluster inconsisten, VERY BAD

    Make sure checkKeepGci is also run on oldStoredReplicas
      to prevent keepgci to move backwards when crash node restarts

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