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

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

Fixed memory overrun when doing REPAIR on table with multi-part auto_increment key where one part was a packed CHAR

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

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

   as requested by PeterZ

   a node name was changed in manual.texi which resulted in a very large
   ReadMe.txt file, as the generating script could not find the (renamed)
   ending node. Fixed the ending node name in Docs/Makefile.am and the 
   Docs/Support/generate-text-files.pl Perl script to make sure this does
   not happen again (I only discovered this because the Do-pkg script was
   not able to add the ReadMe.txt to the Apple Disk image because it ran out
   of disk space due to the size of the file)

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

   in mysqld_safe (commented out by default), to not override any options
   defined in my.cnf (thanks to Axel Schwenke from Jobpilot.de for the
   suggestion)

Fixed test for binary build

  Correct a misleading error message about max row length

  Revert the previous patch: MySQL would not allow creation of VARCHAR columns whose total max length is > 8000 bytes, though InnoDB can easily store them as trailing spaces are removed

  Fix wrong error message: If one tried to create table with a very big row len, MySQL claimed the max len is 64 kB for InnoDB, while it normally is 8000 bytes

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

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

Changed is_open() to work as before.
Added back inited argument to LOG

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

  Put back a 50 millisecond sleep in too high concurrency situations which I removed in the previous push; count also such sleeping threads to the InnoDB queue in SHOW INNODB STATUS

  Fix a benign bug introduced in 4.0.14: InnoDB could complain 'Error: trying to declare trx to enter InnoDB' if several threads tried to init the auto-inc counter for the same table at the same time; in theory, the bug could even lead to a hang of the server, but that shuld be extremely improbable

  Allow also O_DIRECT as innodb_flush_method; it only affects writing to data files

  fix typo.

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

   port number can be different from 3306 when doing the release builds
   with Do-compile, therefore it has to be replaced with the correct
   value during the test run using the "--replace_result" function.

   ChangeSet was not sufficient to get the full ChangeLog between two
   released versions (when using "--changelog=last") as merging between 
   trees also merges the BK tags. Now we explicitely search for the last
   tagged ChangeSet that matches our major+minor version number, which 
   should match the last ChangeSet used for the previous release.

a safer way of initing the mutexes in MYSQL_LOG.
is_open() is now always thread-safe.
See each file for details.

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