unknown event'

   Christian Hammers for providing this patch

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

   discovering this)

  Give sensible advice to the user if InnoDB notices index corruption

into eagle.mysql.r18.ru:/home/vva/work/LOADDATA_BUG/mysql-4.0

into eagle.mysql.r18.ru:/home/vva/work/LOADDATA_BUG/mysql-4.0

  No buffer pool activity in SHOW INNODB STATUS actually meant no page gets

  If HAVE_purify is defined, define UNIV_SET_MEM_TO_ZERO to eliminate Purify warnings

  Do not set buffer pool to zero when we start up: that takes too much time for big buffer pools; Purify users must define UNIV_SET_MEM_TO_ZERO in univ.i to eliminate spurious (?) Purify warnings

  Prevent crash if MySQL calls rnd_end WITOUT calling rnd_init first: only restore active_index if it the old value was pushed in rnd_init
  Initialize active_index to a sensible value: prevent crash if we restore it to the original value after an table scan

  Make InnoDB to restore old active_index value after a table scan: MySQL may assume that a scan does NOT change active_index; this partially fixes bug 241 of UPDATE ... ORDER BY ... but it still remains that MySQL actually ignores the ORDER BY for both MyISAM and InnoDB tables
log0recv.c:
  Use fflush to make sure report of a corrupt log record is printed to .err log before mysqld crashes

  Do not allow InnoDB to cache result set in HANDLER because user can use PREV and NEXT and scroll the cursor

  Allow HANDLER PREV and NEXT also after positioning the cursor with a unique search on the primary key

  Better fix for the ON DELETE SET NULL problem

  Fix bug: we did not allow ON DELETE SET NULL to modify the same table where the delete was made; we can allow it because that cannot produce infinite loops cascaded operations

  Fix crash in HANDLER PREV or NEXT if the cursor was positioned using a unique search condition on the primary key: in that case InnoDB does NOT store the cursor position for later fetch prev or next

into deer.mysql.r18.ru:/home/hf/work/mysql-4.0.erf

  Merge InnoDB-4.0.13; DROP FOREIGN KEY now works

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

Added logging of warnings for failed connections with ssl.
Fixed bug in symbolic link handling on Windows

   (bug #223)
 - Added more detailed info about how to set up replication

   (bug #264)

 - added Dummy file Docs/manual_toc.html to make "make dist" happy if the
   real manual.texi has not been copied into Docs/ (which would make sure
   a "real" manual_toc.html would be created
 - fixed symlinking in the bdb subdirectory (docs are not included anyway)
 - added dist-hook to Makefile.am to remove superfluous SCCS directories
   from the source distribution

 - adjusted LSB run levels to be identical as on Red Hat (2-5)

   libraries always ended up in "dir..", even though they were not supposed
   to be installed anyway (they are only required at link time). Fixed it by
   replacing libs_LIBRARIES with noinst_LIBRARIES for all InnoDB Makefile.am 
   files and by removing "libsdir = " from innobase/include/Makefile.i .

   in the sample configuration files
 - reworked the replication options and comments a bit
 - added option "skip-networking" (commented out by default) to the
   sample configuration files (enhancement request from bug report #234)

   to run the script even if mysqld is not up and running on upgrade

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

(3.23 master, 4.0 slave. 
Slave loss temp tables everytime FLUSH LOGS on master). 
This fix is less bad than the bug, it will cause a problem only maybe
if the master dies the hard way (I say maybe because I could not
cause a problem, and I don't see how it could happen).