the fix from 5.0 with necessary modifications applied.

into  mysql.com:/home/elkin/MySQL/MERGE/5.1-new

into  mysql.com:/extern/mysql/5.1/generic/mysql-5.1-new

into  mysql.com:/usr/local/home/marty/MySQL/mysql-5.1-new

into  mysql.com:/usr/local/home/marty/MySQL/mysql-5.0

into  mysql.com:/usr/local/home/marty/MySQL/mysql-5.1-new

into  mysql.com:/usr/local/home/marty/MySQL/mysql-5.1-new

into  mysql.com:/data0/knielsen/mysql-5.0-mtr-fix

into  mysql.com:/usr/local/mysql/mysql-5.0-mtr-fix

into  zippy.(none):/home/cmiller/work/mysql/merge/mysql-5.1-new

into  zippy.(none):/home/cmiller/work/mysql/merge/mysql-5.1-new

Merge by hand.  This may not be right.

into  april.(none):/home/svoj/devel/mysql/merge/mysql-5.1-new

into  mysql.com:/usr/local/home/marty/MySQL/mysql-5.1-new

Fix for Bug #17840  mysqldump should not dump tables in database cluster, skip cluster internal database

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

into  mysql.com:/data0/knielsen/mysql-4.1-mtr-fix

into mysql.com:/M50/mysql-5.0

into  production.mysql.com:/usersnfs/rkalimullin/4.1.b17896

into  polar.kitebird.com:/src/extern/MySQL/bk/mysql-5.0

into  polar.kitebird.com:/src/extern/MySQL/bk/mysql-4.1

into  polar.kitebird.com:/src/extern/MySQL/bk/mysql-5.0

  myisam_ftdump options: --help first, then rest in
  lexical order.

into  mysql.com:/usr_rh9/home/elkin.rh9/MySQL/Merge/5.0

into  mysql.com:/usr_rh9/home/elkin.rh9/MySQL/Merge/5.0

The fix refines the algorithm of generating DROPs for binlog. 
Temp tables with common pseudo_thread_id are clustered into one query. 
Consequently one replication event per pseudo_thread_id is generated.

accounting non-ai32 in tmpkeyval. This changeset is supposed to be specifically for 4.1.
Another changeset is going to push into 5. 

into  mysql.com:/home/alexi/innodb/mysql-5.1

into  mysql.com:/home/alexi/innodb/mysql-5.1

into  mysql.com:/usr_rh9/home/elkin.rh9/MySQL/Merge/5.0

into  mysql.com:/usr_rh9/home/elkin.rh9/MySQL/Merge/5.0