most InnoDB threads are not terminated properly and the buffer pool is not flushed
to disk. Still no committed transaction is lost as we flush the logs to disk.
InnoDB does crash recovery at startup after this shutdown.
Using this shutdown in testsuite (mysql-test-run --mysqld=--innodb_fast_shutdown=2) saved 3 minutes (13% of total time).

into hundin.mysql.fi:/home/heikki/mysql-5.0

  Add fault tolerance in the scan of .ibd files at a crash recovery; formerly a single failure of readdir_get_next caused the rest of the directory to be skipped

                overwrites IN variable
  and added error checking of variables for [IN]OUT parameters while
  rewriting the out parameter handling.

into mysql.com:/space/my/mysql-4.1

into mysql.com:/space/my/mysql-5.0

into mysql.com:/space/my/mysql-4.1-build

into mysql.com:/export/space/pekka/ndb/version/my41

into mysql.com:/space/my/mysql-5.0

into mysql.com:/usr/home/ram/work/mysql-5.0

into mysql.com:/usr/home/ram/work/mysql-4.1

into mysql.com:/space/my/mysql-4.1-build

into mysql.com:/space/my/mysql-5.0-build

into mysql.com:/usr/home/ram/work/5.0.bit_class

into mysql.com:/home/matthias/Arbeit/mysql-4.1/src-clean

into mysql.com:/space/my/mysql-5.0-build

into mysql.com:/space/my/mysql-4.1-build

  Add a big fat warning for future programmers that MySQL may call ::store_lock() also with lock 'type' TL_IGNORE; my ignorance of this caused bug 9670

into hundin.mysql.fi:/home/heikki/mysql-5.0

set_bit replaced with internal_set_bit,
clear_bit replaced with internal_clear_bit.

into rurik.mysql.com:/home/igor/dev/mysql-5.0-0

  Added a test in connection with the fix for
  bug #6106.
view.result, view.test:
  Added test cases for bugs #6106/6107.
sql_show.cc:
  The addition of the case for items of the type REF_ITEM in the
  function uses_only_table_name_fields became necessary after
  the fix for bug #6106.
sql_base.cc:
  The problem was due to the fact that two different column
  references were glued together though one of them belonged to
  a subquery while another to an outer query. This caused
  eventually a wrong calculation of values for the used_tables
  attribute.

into mysql.com:/export/space/pekka/ndb/version/my41

into mysql.com:/home/cps/mysql/trees/mysql-5.0

into mysql.com:/home/jimw/my/mysql-5.0-clean

into mysql.com:/space/my/mysql-4.1-build

into mysql.com:/space/my/mysql-5.0-build

into mysql.com:/space/my/mysql-4.1-build

- fixed a date for a changelog entry  in the RPM spec file (s/Mar/Apr/) - RPM complains about wrongly
  ordered entries.

  Fix part of bug #9670: if MySQL calls ::store_lock with TL_IGNORE, do not change prebuilt->select_lock_type; this fix may heal the assertion failures reported in UPDATE and multi-table UPDATE; it is not clear if this fixes the problems in OPTIMIZE TABLE