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

Simple cleanup of previous pull

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

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

properly fixed in 4.1

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

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

Added MAX_PASSWORD_LENGTH. This increased master-slave passwords to 32 bytes (Bug #766)
Fixed server crash on purge master logs or show master logs when binlog is off. (Bug #733)

A security leak with SHOW TABLES/ TABLE STATUS FROM db ...

  Since the mysql interactive client or some other phase in communication cuts > 64 kB strings to very short, restrict the output of SHOW INNODB STATUS to at most 60 kB

  Remove potential starvation of a full log buffer flush: only flush up to the lsn which was the largest at the time when we requested the full log buffer flush
os0sync.h, os0sync.c:
  Fix a bug in os_event on Unix: even though we signaled the event, some threads could continue waiting if the event became nonsignaled quickly again; this made group commit less efficient than it should be

into deer.(none):/home/hf/work/mysql-4.0.739

check for negative count in RPAD added

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

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

Remove unaligned warnings on Ia64 from client library when using --host
Fix for replication when using many file descriptors 

Fields in key_expr (mysql_ha_read) wasn't linked to tables.
Hmm. How did it work at all?

  Fix bug: group commit still did not work when we had MySQL binlogging on

into deer.(none):/home/hf/work/mysql-4.0

into mysql.com:/home/pz/mysql/mysql-4.0-root

The changes for actual loads and memory sizes are to be done after
text and format are  improved.

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

into deer.(none):/home/hf/work/mysql-4.0.717

into deer.(none):/home/hf/work/mysql-4.0.628

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

Tests cleanup (put drop database first in tests)

Current table is placed into read_tables set of the current join_tab->select
so get_mm_parts function thinks that current table's record is read and
tries to calculate WHERE condition with the fields of the record.
Result of these calculations is unpredictable.
Looks funny - outcome of the SELECT depends on the queries executed before.

Anyway i think we should have testcase on this part of the code.

  Remove outdated comment and the corresponding assertion in debug version code