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

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

Accept zero dates without warnings

  Remove the flag HA_NOT_READ_PREFIX_LAST because ORDER BY orders wrong then; also remove the diagnostic print to avoid cluttering the error log

  Move to the right place the flag which bans use of HA_READ_PREFIX_LAST; add diagnostics and remove the assertion on line 2180 of ha_innodb.cc

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

 - mysql.spec.sh: MySQL-Max now requires MySQL >= 4.0 to avoid version
   mismatches (people were mixing MySQL 3.23 and 4.0 RPMs)

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

   and applied some cosmetical fixes

manual.texi	and QUICK are not mutually exclusive).

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

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