15 seconds to less than a second.
The sleeps used to be necessary but not anymore as NDB has been fixed
wrt sync_slave_with_master.

into  romeo.(none):/home/bk/b17620-mysql-5.1-new-rpl

Invalidating query cache when processing rows for a statement on the slave.

into  romeo.(none):/home/bkroot/mysql-5.1-new-rpl

into  andrepl.dsl.inet.fi:/home/elkin/MySQL/TEAM/FIXES/5.1/wl3368_mixed_default

Two minor fixes:
 1. to make make test executes with mixed;
 2. proper isolation of binlog_statement_insert_delayed 
    from others through reset master cleaning up binlog
    todo: adapt this technique to other restarting for binlog tests

into  romeo.(none):/home/bk/mysql-5.1-new-rpl

into  andrepl.dsl.inet.fi:/home/elkin/MySQL/TEAM/FIXES/5.1/wl3368_mixed_default

   The following is an excerption from the WL.
      
   1. Change so that MIXED is default format
      1.1 to change the default for command line --binlog-format
      1.2 to alter global_system_variables.binlog_format calculation
          basing on command line --binlog-format parameter and 
          its default.
   2. Change test suite so that more testing is done by MIXED format.
      2.1 to check if there are test cases requiring --binlog-foramt=statement via
          `source include/have_binlog_format_statement.inc' and affected by 
          altering the latter to be "mixed".
      2.2 to check the content of such vulnerable cases to find if
          extending to the mixed does not modify results. In that case simply
          substitute source arguments as explained.
      2.3 if a test in mixed mode deals with features triggering
          row-binlogging then if necessary we can switch explicitly
          to statement mode or create another test to run with 
          non-recommended STATEMENT mode
   
          Particullarily, extracting INSERT DELAYED 
          binlogging subtest for statement mode is performed, and 
          the snippet is moved into a separate test file.
          Note that since now all three modes verify this use case
          through 3 different tests.
   
   No changes in item 3 of HLD appeared to be needed.

Adding condition to ensure that mutex are locked and unlocked
under same condition.

into  production.mysql.com:/usersnfs/mkindahl/mysql-5.1-clone

Post-merge fixes.

into  romeo.(none):/home/bk/w3259-mysql-5.1-new-rpl

Post-merge fixes.

Fix to allow the binlog format to be changed between the LOCK and
UNLOCK tables, as well as under MIXED mode.

into  mysql.com:/users/lthalmann/bk/MERGE/mysql-5.1-merge

into  mysql.com:/users/lthalmann/bk/MERGE/mysql-5.0-merge

into  mysql.com:/users/lthalmann/bk/MERGE/mysql-5.1-merge

into  mysql.com:/users/lthalmann/bk/MERGE/mysql-5.0-merge

into  mysql.com:/users/lthalmann/bk/MERGE/mysql-4.1-merge

 Fixing test result.

 the usable range to 0..1000 (0 disables the thread throttling).

into  rama.(none):/home/jimw/my/mysql-5.1-clean

into  bodhi.local:/opt/local/work/mysql-5.1-runtime-merge

 - Add loop in mysqlslap that tries to connect up to 10 times if connect
   in thread fails.