(this bug was already fixed in 4.0, I just copied and pasted two lines).

into eagle.mysql.r18.ru:/home/vva/work/LOADDATA/mysql-3.23

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

  Backport from 4.0: We had forgotten to call pthread_mutex_destroy when we free an OS mutex in Unix

Security patch to remove wrong error when one had a global update/delete privilige and a database specific SELECT privilege. 

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

All tests plus grant.pl test passed.

into sinisa.nasamreza.org:/mnt/work/mysql

into serg.mylan:/usr/home/serg/Abk/mysql

Backported fix from 4.1 for bug 212: SELECT query containing a NATURAL JOIN and parentheses in the WHERE clause

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

Fixed problem with not freed thr_alarm() on slave connect

logged, but read as LOAD DATA INFILE REPLACE"
This was just bad && instead of &, but nasty consequences.
This should be merged to 4.0 BUT it will not be automatic (some code
has moved from log_event.h to log_event.cc, and log_event.cc has changed);
please Merging Man, do 'bk grep REPLACE_FLAG' in 4.0/sql
to find all the new places.

least one BLOB column.

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

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

only do it if the user specifies --delete-master-logs (new option).
Safer + fixes bug #159.

into serg.mysql.com:/usr/home/serg/Abk/mysql

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

  Test if merging from 3.23 to 4.0 succeeds

  Fix bug number 154: GROUP BY and DISTINCT could treat NULL values inequal

 - bumped up version number to 3.23.57 in configure.in

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

  Fix bug: MySQL could erroneously return Empty set if InnoDB estimated index range size to 0 records though the range was not empty; MySQL also failed to do the next-key locking in the case of an empty index range