misprint correction

  (bug #141) (please merge with 4.1 and onwards)

INSERT DELAYED.

now we'll have something like this :
030308 18:46:58  Slave I/O thread: connected to master 'gb@localhost:3306',  replication started in log 'FIRST' at position 4
030308 18:46:58  While trying to obtain the list of slaves from the master 'localhost:3306', user 'gb' got the following error: 'Access denied. You need the REPLICATION SLAVE privilege for this operation'
030308 18:46:58  Slave I/O thread exiting, read up to log 'FIRST', position 4
instead of "Error updating slave list: Query error".
This fixes bug #80.

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

Some after merge fixes

  Fix bug in previous push

  Print and error message also if a read from file results in the Linux error EEXIST; may happen if the disk is broken

Now log_pos is the real position of the event. For events that are between BEGIN and COMMIT,
log_pos is still the BEGIN's log_pos.
This fixes bug #52 (If only transactions are run on the master then t

"very new functions" - for now 4.1-compatible TIMESTAMT format

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

   redirected to the new location

   (Bug #121)

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

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

  Change mode to -rwxrwxr-x

   distribution to fix a test failure in test "func_encrypt"

  Add comment that Guilhem should check master_log_name, pending etc are right if the master log gets rotated

  Remove (already commented out) code about storing the latest relay log pos info to InnoDB: we will probably use only the master log pos info when we restart a slave after a crash

  Do not try to resolve the table name of a corrupt page if the code is in ibbackup, i.e., the dict system is not initialized

Fixed bug in LOCK TABLE + DROP TABLE when other thread was waiting for a table that was locked bug not droped