This allows one to setup a master <-> master replication with non conflicting auto-increment series.
Cleaned up binary log code to make it easyer to add new state variables.
Added simpler 'upper level' logic for artificial events (events that should not cause cleanups on slave).
Simplified binary log handling.
Changed how auto_increment works together with to SET INSERT_ID=# to make it more predictable: Now the inserted rows in a multi-row statement are set independent of the existing rows in the table. (Before only InnoDB did this correctly)

into mishka.local:/home/my/mysql-5.0

Fixed (together with Guilhem) bugs in mysqlbinlog regarding --offset
Prefix addresses with 0x for easier comparisons of debug logs
Fixed problem where MySQL choosed index-read even if there would be a much better range on the same index
This fix changed some 'index' queries to 'range' queries in the test suite
Don't create 'dummy' WHERE clause for trivial WHERE clauses where we can remove the WHERE clause.
This fix removed of a lot of 'Using where' notes in the test suite.
Give NOTE instead of WARNING if table/function doesn't exists when using DROP IF EXISTS
Give NOTE instead of WARNING for safe field-type conversions

  Easy to prevent crash, but the question was how to treat this case?
  We ended up implementing the "global" SPs (i.e. with no associated
  db), which were planned but left unresolved when SPs moved into dbs.
  So now things like "call .p()" work too.

  Althought techically not a but (as it's functioning as designed),
  it was decided that the design should be changed. Some users have
  a problem with dates being '0000-00-00' and the SQL standard specifies
  that the modification date should be the same as the creation date
  at creation.

into mishka.local:/home/my/mysql-5.0

into silver_beast.(none):/home/cps/mysql/devel/im/default_patch/mysql-5.0

into silver_beast.(none):/home/cps/mysql/devel/im/default_patch/mysql-5.0

final 0 of the string.

(Includes merge of arena code in 4.1 and 5.0)

into silver_beast.(none):/home/cps/mysql/devel/im/default_patch/mysql-5.0

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

into gluh.mysql.r18.ru:/home/gluh/MySQL-BUGS/mysql-4.1

server': the bug occurs when arguments of LIKE function are in 
differentcharacter sets. If these character sets are compatible, 
we create an item-converter. In prepared mode, this item
needs to be created in memory of current prepared statement.

Merged the different find_xxxx_table_in_list functions to one + some inline functions

  Allow FROM or IN in SHOW KEYS, as in other SHOW statements.

mysql_create_system_tables, just in case

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

2. changed key_* to el_ley_* in the libedit key.h
   (because it's in the conflict with the aix definitions)
3. use libedit_term.h instead of term.h in the cmd-line-utils/libedit/el.h
4. added definition of MIN in the cmd-line-utils/libedit/read.c 
   (if it wasn't defined yet)
5. discarded definition of SUNOS macro from configure.in 
   (now we don't include term.h in the el.h at all)

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

Add missing parameter to strxnmov() that caused some INTO OUTFILE commands to core dump

  Add GPL comment

into mysql.com:/Users/mikron/mysql-4.1