this is better in this case:
- imagine user1 has created a temp table
- imagine user2 does FLUSH TABLES WITH READ LOCK, then takes a backup,
then RESET MASTER then UNLOCK TABLES, like mysqldump --first-slave
- then in the binlog you will finally have the DROP TEMPORARY TABLE,
but not the CREATE TEMPORARY TABLE, so when you later restore with
mysqlbinlog|mysql, mysql will complain that table does not exist.
Replication was already protected of this (it processes DROP TEMPORARY
TABLE as if there was a IF EXISTS), now I add it directly to the query
for mysqlbinlog|mysql to work.

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

with a testcase.
We needed to init_master_info before we flush_master_info
in LOAD DATA FROM MASTER.

into teton.kitebird.com:/home/paul/mysql-4.0

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

into gluh.mysql.r18.ru:/home/gluh/Bugs/mysql-4.0.3067

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

  Fix for a bug in the result
multi_update.test:
  Fix for a bug in the test

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

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).