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

  Sinisas patch to InnoDB ORDER BY DESC bug, push it now so that Jani has it available

Added ALL as parameter option for all group functions.
Make join handling uniform. This allows us to use ',', JOIN and INNER JOIN the same way.
Sort NULL last if DESC is used (ANSI SQL 99 requirement)

 - add version number to build log files (e.g. Logs/build-4.1-standard.log)
 - add host name and uname to Subject line of build failure mails
   (e.g. "Subject: build(Linux): mysql-4.1-standard compilation failed")

 -> Please merge with all other trees!

   the --password parameter (better add it to my.cnf instead) (Thanks to
   Christian Hammers for the suggestion)

   address to report bugs to bugs@mysql.com (thanks to Christian Hammers
   for pointing this out) - please merge this into all other trees!

  new file
.del-overlay.tar.gz~5bd3087e191e7574:
  Delete: netware/overlay.tar.gz

  Backport from 4.0: fix potential bug if store_lock is called with TL_IGNORE in the middle of a query

  Fix potential bug: if MySQL calls store_lock with the TL_IGNORE argument in the middle of query processing, then InnoDB select_lock_type could be reset to LOCK_NONE in a wrong place