into mysql.com:/home/mysql_src/mysql-4.0

(--local-load alone means "I want files to be prepared for LOAD 
DATA INFILE, in the default temp directory", and mysqlbinlog already
does this without --local-load).

into hundin.mysql.fi:/home/marko/l/mysql-4.0

into eagle.mysql.r18.ru:/home/vva/work/BUG_2985/mysql-4.0

Ensure that install_test_db.sh script works with both 'make install' and 'make_binary_distribution' layouts
Abort if we can't allocate memory for table cache
Fix bug with multi-update-tables and BDB tables.

into hundin.mysql.fi:/home/marko/l/mysql-4.0

into sinisa.nasamreza.org:/mnt/work/mysql-4.0

  Test case for a #2996 bug fix
multi_update.test:
  test case for a #2996 bug fix
sql_select.cc:
  Fix for a bug #2996 involving multi-table updates over the const tables

We introduce a new function mysql_test_parse_for_slave().
If the slave sees that the query got a really bad error on master
(killed e.g.), then it calls this function to know if this query
can be ignored because of replicate-*-table rules (do not worry
about replicate-*-db rules: they are checked so early that they have
no bug). If the answer is yes, it skips the query and continues. If
it's no, then it stops and say "fix your slave data manually" (like it
did before this change).

into mysql.com:/home/mysql_src/mysql-4.0

re-using unused LOCK_active_mi to serialize all administrative
commands related to replication:
START SLAVE, STOP SLAVE, RESET SLAVE, CHANGE MASTER, init_slave()
(replication autostart at server startup), end_slave() (replication
autostop at server shutdown), LOAD DATA FROM MASTER.
This protects us against a handful of deadlocks (like BUG#2921
when two START SLAVE, but when two STOP SLAVE too).
Removing unused variables.

into hundin.mysql.fi:/home/marko/l/mysql-4.0

into sinisa.nasamreza.org:/mnt/work/mysql-4.0

into ua72d24.elisa.omakaista.fi:/home/my/bk/mysql-4.0

into hundin.mysql.fi:/home/marko/l/mysql-4.0

into eagle.mysql.r18.ru:/home/vva/work/BUG_2874/mysql-4.0

  reverting fix

  Print always the count of pending pread() and pwrite() calls if there is a long semaphore wait

  Do not test a magic number with =, use == instead :)

into eagle.mysql.r18.ru:/home/vva/work/BUG_2874/mysql-4.0

into eagle.mysql.r18.ru:/home/vva/work/BUG_2874/mysql-4.0

added tests for testing structure of mysql db

ChangeSet 1.1620.12.1 and ChangeSet 1.1625.2.1
from 4.1. This makes the slave I/O thread flush the relay log 
after every event, which provides additional safety in case
of brutal crash (reduces chances to lose a part of the relay log).

- the one about BUG#2921
- the one about relay log flushing
Both will be rewritten in a next changeset
(this one will not be pushed before the next changeset).

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