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

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

   ANALYZE TABLE)

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

  Don't allow access outside the string

   instead of being an individual file to avoid redundancy

  When FLUSH LOGS is called, flush InnoDB logs to disk also in the case innodb_flush_log_at_trx_commit=0

  Make sure we do not do insert buffer merge in fast shutdown even if there is some buglet which increments srv_activity_counter during a shutdown

  Make buffer pool flush batches bigger as that may save some time if fsync is very inefficient

  Make ANALYZE TABLE to update index cardinality and other statistics also for an InnoDB table; note that the estimates are based on 10 random dives, not on an exhaustive read of the table

(There was a problem on some AMD system when the floating point precision wasn't accurate enough)

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

into mysql.com:/home/pgulutzan/mysql-4.0

from Monty.

Added optimzation for clustered index
Fixed bug in UPDATE ... ORDER BY
Fixed handling of UPDATE ... LIMIT

  Enable 'LOAD LOCAL INFILE', for parity with unix binaries.

more detailed explanation of record header and column 
storage.

unknown event'

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

   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