srv_lock_timeout_and_monitor_thread(): write to srv_monitor_file
  only if --innodb_status_file=1

(Cleanups and better bug fixes)

into mysql.com:/home/timka/mysql/src/4.0-master

into mysql.com:/space/bk/b6148-mysql-4.0

slave SQL thread is started.

to run the standard tests with "--force" (default, can be switched off).

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

  bug#6705 - (+trunc1* +trunc2*)
fulltext.test, fulltext.result:
  bug#6705

into mysql.com:/home/dlenev/src/mysql-4.0-bg6439

When mysqlbinlog prints LOAD DATA INFILE, let it print the thread id. Some customer would have benefited
much from this in his recovery. All this change does is adding one commented (#) line before the LOAD DATA
command, so it is quite innocuous.

  Fix InnoDB bug #6287: if one uses INSERT IGNORE to insert several rows at a time, and the first inserts are ignored because of a duplicate key collision, then InnoDB in a replication slave assigns AUTO_INCREMENT values 1 bigger than in the master

values for too big argument".

Added range checking for from_unixtime() argument, cleaned up code 
a bit.

were stopping at docid 0xffffffff

  Add -acc flag for texi2html to handle accented characters.

into gw.mysql.r18.ru:/usr/home/ram/work/4.0.b6564

  Prevent creation of a row which grants no rights
  Test included

into kite-hub.kitebird.com:/src/extern/MySQL/bk/mysql-4.0

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

When we are writing a transaction to the binlog, we log BEGIN/COMMIT with zero error code.
Example: all statements of trans succeeded, connection lost and so implicit rollback:
we don't want ER_NET* errors to be logged in the BEGIN/ROLLBACK events, while statement
events have 0. If there was really a serious error code, it's already in the statement events.

Revise the --hex-blob help message string. (This will need
revising after merge to 4.1, too, but the CHAR BINARY and
VARCHAR BINARY data types will be BINARY and VARBINRY.)

  Adding a prototype for the new function.

--defaults-extra-file option.

into a193-229-222-105.elisa-laajakaista.fi:/home/my/bk/mysql-4.0

my.cnf from the default directories.

  Dump VARCHAR(n) BINARY in HEX if --hex-blob too.

this is important because this 4.0 "Bootstrap" is the one generally used on host "build".

  Backport --hex-blob to 4.0

  After-merge clean-up

  Clean-ups

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