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

into beta.frontier86.ee:/stuff/bk/mysql-4.0

  Contrib overhaul

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

into sanja.is.com.ua:/home/bell/mysql/work-4.0

FN_NO_CASE_SENCE used instead of __WIN__ in table name handling of quary cache

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

into work.mysql.com:/d1/users/mwagner/work/bk/mysql-4.0

manual.texi	missing from the syntax diagram.

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

  InnoDB does allow a foreign key constraint name to be specified

  InnoDB does allow a foreign key constraint name to be specified, though it is not used in any way

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

   up-to-date BK changelog instead of sql/ChangeLog, add LICENSE if
   available)

Don't require UPDATE_ACL for REPLACE

 - some additional small fixes
 - added "depcomp" for automake 1.5

 - added some missing changelog entries to the 4.0.5 changelog
 - applied small fix to configure.in from monty (already applied manually
   to configure.in of the 4.0.4 release source files - not relevant for
   normal builds anyway)

  Clarified FOREIGN KEY syntax, added a note that CREATE TABLE causes an InnoDB commit if binlogging is used, added InnoDB version history