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

 - 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

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

   common, especially on our main build systems
 - cosmetical fix in mysql.spec

   message on STDOUT on AIX and assigned the wrong value)

into hundin.mysql.fi:/my/bk/mysql-4.0

  Remove 'web clients' contrib section

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

  Clean out 'Graphical clients' section of the contributed software section

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

  Put the flag HA_NOT_READ_PREFIX_LAST back to index_flags: seems to fix also the LIKE ... DESC bug

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

   with InnoDB support when requested to do so)

  Fix an assertion in btr0pcur.c line 203 when an UPDATE is done inside LOCK TABLES

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

into mysql.com:/home/nick/mysql/repository/mysql-4.0