Added more DBUG statements
Ensure that we are comparing end space with BINARY strings
Use 'any_db' instead of '' to mean any database. (For HANDLER command)
Only strip ' ' when comparing CHAR, not other space-like characters (like \t)

caused UDF functions to segmenation fault when they tried to
print an error during wrong usage.

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

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

Don't use --command in tests; use command.

  Allow always DROPping of a table which is only referenced by FOREIGN KEY constraints from the same table
Many files:
  Do not let REPLACE to perform internally an UPDATE if the table is referenced by a FOREIGN KEY: the manual says that REPLACE must resolve a duplicate key error semantically with DELETE(s) + INSERT, and not by an UPDATE; the internal update caused foreign key checks and cascaded operations to behave in a semantically wrong way

  Fix crash in InnoDB RENAME TABLE if 'databasename/tablename' is shorter than 5 characters (Bug #2689); reported by Sergey Petrunia

into mysql.com:/home/kostja/mysql/mysql-4.1-root

don't set other flags: it breaks future extensions

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

Removed warnings from test suite

Fixed output from mysqlbinlog when using --skip-comments
Fixed warnings from valgrind
Fixed ref_length when used with HEAP tables
More efficent need_conversion()
Fixed error handling in UPDATE with not updateable tables
Fixed bug in null handling in CAST to signed/unsigned

alter table rename a bit more efficient in case of
lower_case_table_names.

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

  Fix bug #2167: generate foreign key id's locally for each table, in the form databasename/tablename_ibfk_number; if the user gives the constraint name explicitly remember it; these changes should ensure that foreign key id's in a slave are the same as in the master, and DROP FOREIGN KEY does not break replication
sync0sync.c:
  UNIV_SYNC_DEBUG caused assertion in the creation of the doublewrite buffer, if we do not allow thousands of latches per thread

  If AUTOCOMMIT=1, then we do not need to make a plain SELECT set shared locks even on the SERIALIZABLE isolation level, because we know the transaction is read-only: a read-only transaction can always be performed on the REPEATABLE READ level, and that does not endanger the serializability

into mysql.com:/home/kostja/mysql/mysql-4.0-merge

http://bugs.mysql.com/bug.php?id=2366
Wrong utf8 behaviour when data is trancated

   1.5 to fix BUG#202 (update config.guess & co for MIPS architecture)

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

   so it gets picked up by "make dist" and updated init_file test accordingly.

into eagle.mysql.r18.ru:/home/vva/work/BUG_2310/mysql-4.1

into eagle.mysql.r18.ru:/home/vva/work/BUG_2526/mysql-4.0

into eagle.mysql.r18.ru:/home/vva/work/BUG_2526/mysql-4.0