into build.mysql.com:/users/tulin/mysql-5.0-ndb

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

into here.mwagner.org:/Users/mwagner/work/bk/mysql-5.0

  Use the invisible tabs (!)

into kite-hub.kitebird.com:/src/extern/MySQL/bk/mysql-5.0

  Fix test result affected by error message rewording.
errmsg.txt:
  Reword error messages.
set_var.cc:
  Reorder variables.
mysqld.cc:
  Reorder options.

into here.mwagner.org:/Users/mwagner/work/bk/mysql-5.0

  Add missing 'get_defaults_files' to fix linking error.

into build.mysql.com:/users/tulin/mysql-5.0-ndb

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

    search for subscriber should be done on nodeid basis and not reference, only one subscriber per event per nodeid allowed
    not necessarily the same starts and stops...
    +error corrected in ref signal
    added print of error codes + more correct error handling of event errors
    + added goto instead of erroneous break to fix bug#7627

into kite-hub.kitebird.com:/src/extern/MySQL/bk/mysql-5.0

into build.mysql.com:/users/tulin/mysql-5.0-ndb

into mysql.com:/dbdata/psergey/mysql-5.0-bug5401-2

into build.mysql.com:/users/tulin/mysql-5.0

into kite-hub.kitebird.com:/src/extern/MySQL/bk/mysql-5.0

into build.mysql.com:/users/tulin/mysql-5.0-ndb

into build.mysql.com:/users/tulin/mysql-5.0

  Logging to logging@openlogging.org accepted
innodb.result, innodb.test, set_var.cc, mysqld.cc:
  change variable innodb_free_tickets_to_enter to innodb_concurrency_tickets

into kite-hub.kitebird.com:/src/extern/MySQL/bk/mysql-5.0

into mysql.com:/home/jwinstead2/mysql-5.0-clean

into build.mysql.com:/users/tulin/mysql-4.1

into build.mysql.com:/users/tulin/mysql-4.1

into mysql.com:/home/jwinstead2/mysql-5.0-clean

into kite-hub.kitebird.com:/src/extern/MySQL/bk/mysql-5.0

into hundin.mysql.fi:/home/heikki/mysql-5.0

  Add comments about why the InnoDB latching order is obeyed also for the MySQL query cache mutex; add an error printf if that is not the case
sync0sync.h:
  Assign sync0sync.h ranks also for the MySQL query cache mutex and the MySQL binlog mutex; the latching order must be obeyed also for these
row0ins.c:
  Add a comment why the query cache invalidate operation cannot deadlock in a cascaded FOREIGN KEY operation

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

into mysql.com:/home/jwinstead2/mysql-5.0-clean

into kite-hub.kitebird.com:/src/extern/MySQL/bk/mysql-5.0