into mysql.com:/home/greg/bk/mysql-4.0

  new file

  Add comment about how to modify InnoDB to deal with partial-field prefixes of key value in the future

  Add comment about what kind of key value prefixes HA_READ_KEY_PREFIX_LAST etc. allow as a search key

  Prepare for 5.x where HA_READ_PREFIX_LAST may pass only a few first bytes of the last field in a key value
ha_innodb.cc:
  In 4.0 always assume HA_READ_PREFIX_LAST passes a complete-field prefix of a key value; LIKE queries use a padding trick

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

Novell patches

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

Reverted wrong patch for mysqld_safe.sh

a socket from another, still living MySQL server.

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

 - updated logo to current one

Replaced mysql.de.texi in mysql-4.0 tree with dummy placeholder.
Moved world.sql sample database to mysqldoc tree.

- re-added missing pre- and post(un)install scripts to server subpackage
- added config file /etc/my.cnf to the file list (just for completeness)
- make sure to create the datadir with 755 permissions

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

  new file

Don't make OLD_PASSWORD() a reserved word

  Disable PAGE_CUR_LE_OR_EXTENDS because it does not work for non-latin1 char sets now

  Clarify the meaning of HA_READ_PREFIX_LAST as a search flag. InnoDB assumed the meaning wrong.

  Since MySQL uses HA_READ_PREFIX_LAST in a wrong place, we make InnoDB to convert it to a right search condition