Plus a changeset which I had committed but forgot to push (and this changeset is lost on
another computer, so I recreate it here). This changeset is "user-friendly SHOW BINLOG EVENTS
and CHANGE MASTER TO when log positions < 4 are used.

Bug 571: play LOAD DATA INFILE the same way on the slave as it was on the master: 
if it was with IGNORE, do it with IGNORE,
if it was with REPLACE, do it with REPLACE,
and (the change) if it was with nothing, do it with nothing (not with IGNORE !!).
Bug 573: print a proper error message in case of duplicate entry in LOAD DATA INFILE
on the slave, i.e. a message where the keyname and key value appear :
'Duplicate entry '1' for key 1' and not 'Duplicate entry '%-.64s' for key %d'

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

not the master's binlog) (SW 1571).

  Do not try to reserve os_sync_mutex in shutdown after it has been freed

  Removed auto event creation because it is not needed in any MySQL/InnoDB code

  Put back Monty's patch which the previous push accidentally erased: print also operation type in os_file_handle_error()

  Release all event semaphores at shutdown also in Windows
srv0start.c, srv0srv.c:
  make test sometimes failed because lock timeout thread exited without decrementing the InnoDB thread counter

into narttu.mysql.fi:/my/mysql-4.0

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

into narttu.mysql.fi:/my/mysql-3.23

(Casused problems in GIS functions in 4.1)

  Cleanup
os0sync.c:
  Free all OS sync primitives and allocated memory in InnoDB shutdown

  Free all OS sync primitives and allocated memory in InnoDB shutdown

  Cleanup

  Exit all threads created by innoDB at shutdown

  Prevent the InnoDB main thread from hogging CPU if a table lingers in the background drop queue (though it is essentially a bug if a table end up there at all)

  Fix for multibyte charsets

into narttu.mysql.fi:/my/mysql-4.0

before stopping. This is to make the test's result predictable (depending
on the machine the results could formerly be slightly different, though
everything is sane in the code; it's not a bug).

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

into narttu.mysql.fi:/my/mysql-4.0

Fixed problem with localtime -> gmt where some times resulted in
different (but correct) timestamps. Now MySQL should use the smallest
possible timestamp value in this case.  (Bug 316)

soon.

into narttu.mysql.fi:/my/mysql-3.23

into ua126d19.elisa.omakaista.fi:/home/my/bk/mysql-4.0