we now make a distinction between if the master is < 3.23.57, 3.23 && >=57, and 4.x
(before the 2 3.23 were one). This is because in 3.23.57 we have a way to distinguish between
a Start_log_event written at server startup and one written at FLUSH LOGS, so we
have a way to know if the slave must drop old temp tables or not.
Change: mi->old_format was bool, now it's enum (to handle 3 cases). However, functions
which had 'bool old_format' as an argument have their prototypes unchanged, because
the old old_format == 0 now corresponds to the enum value BINLOG_FORMAT_CURRENT which
is equal to 0, so boolean tests are left untouched. The only case were we use mi->old_format
as an enum instead of casting it implicitly to a bool, is in Start_log_event::exec_event,
where we want to distinguish between the 3 possible enum values.

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

if 'user_name' is the current user and it is not root.

  Revert a change to dict_mem_index_add_field which slipped prematurely into the bk tree

  Fix the BDB crash in the previous push; to save CPU remove duplicate calls of commit in InnoDB

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

in case of an empty string. Bug ID 586.

More debugging variables
Increment aborted_threads in case of killed or too big packet

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

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

   to set CXX=gcc (cannot link the code with g++) - this should help to
   recompile the RPM on Distributions using gcc 3
 - Added a symlink /usr/sbin/rcmysql -> /etc/init.d/mysql

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

   Red Hat's chkconfig (Bug #272) (The LSB spec is a bit ambigous about
   what actually needs to be put into this field)

  If the autocommit is on, let handler.cc commit or rollback the whole transaction at an updating SQL statement end. This probably fixes bug number 578. The problem was that when explicit LOCK TABLES is used, then the lock count method in autocommit does not work.

Portability fix for Windows 64

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

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:/space/my/mysql-4.0

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 mysql.com:/space/my/mysql-4.0

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)