into mysql.r18.ru:/usr/home/ram/work/4.0

"mysqlhotcopy fails to copy tables but does not indicate a failure"
("does not indicate a failure");
this is about "mysqlhotcopy fails to copy tables".

Now INTERVAL(NULL, N1, N2, ...) returns NULL.

into mysql.com:/space/my/mysql-4.0-build

   override CC/CXX when using a special compiler)
 - the RPM should now build on AMD64 and IA64, too

into mashka.mysql.fi:/home/my/mysql-4.0

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

   (BUG#812)

into mashka.mysql.fi:/home/my/mysql-4.0

Removed double my_thread_end() which caused fatal error on windows if mysqld died on startup

  Prevent the user from creating InnoDB tables with > 1000 columns

No commit message

  Undo serg's patch that used my_print_defaults,
  and instead simply do not define $opt{user}.
  This allows the script to use option files properly.

into serg.mylan:/usr/home/serg/Abk/mysql-4.0

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

BUG#797 "If query ignored on slave (replicate-ignore-table) the slave still checks if
the returned error (0) is the same as the one on the master, whereas it shouldn't
test this.
Plus a new test for BUG#797.

  A cosmetic change: set trx id to zero at creation so that SHOW INNODB STATUS does not print a random value for the id of a transaction object for which the transaction has never been started yet (for example, running SHOW INNODB STATUS as the first command from a mysql prompt printed a random id for the trx object associated with the session itself running the SHOW INNODB STATUS command)

into serg.mylan:/usr/home/serg/Abk/mysql-4.0

still no rec. descent

  Fix bug: if a DELETE failed in a FOREIGN KEY error and it had already deleted some rows, then MySQL did not roll back the failed SQL statement, and also wrote it to the binlog

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

FLUSH LOGS now rotates relay logs,
and a new variable max_relay_log_size.
Plus a very small bit of code cleaning.

  Fix performance bug: if there were thousands of tables, DROP TABLE could take as much as a second CPU time

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

  In background loop run purge to completion before doing other background operations: it does not make sense to flush buffer pool pages if they are soon modified again by purge
trx0purge.c:
  Increase purge_sys->n_pages_handled for every undo log we purge, even if that log would be only a hundred bytes: that way we get the purge batches of 20 pages to set a fresh purge view (limit) more often, and we can reduce the number of old row versions purge has to look at when it decides if it can remove some delete-marked index record

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

versions of DBD. New mysqlhotcopy version supports both old
and new DBD versions while versions elder than 1.19 support
only old DBD versions.

into narttu.mysql.fi:/my/mysql-4.0

into serg.mylan:/usr/home/serg/Abk/mysql-4.0

Simple cleanup of previous pull

into mysql.r18.ru:/usr/home/ram/work/4.0

properly fixed in 4.1