This patch simply adds sql_big_selects to the list of variables
  output by SHOW VARIABLES.

This patch restores sync_binlog.

into  perch.ndb.mysql.com:/home/jonas/src/mysql-5.0

into  perch.ndb.mysql.com:/home/jonas/src/mysql-5.0

into  mysql.com:/home/alexi/innodb/mysql-5.0-ss492

into  mysql.com:/home/alexi/innodb/mysql-5.0-ss492

into  mysql.com:/home/alexi/innodb/mysql-5.0-ss492

into  mysql.com:/home/alexi/innodb/mysql-5.0-ss492-work

  clone-off for 5.0.21

into  mysql.com:/home/alexi/innodb/mysql-5.0-ss492-work

 Use files innodb_mysql.[test|result] instead.

into sergbook.mysql.com:/usr/home/serg/Abk/mysql-5.0

 Fixed BUG#19217 "dict_load_indexes() may read the delete-mark incorrectly".

(reported by Stefano Di Paola)

into mysql.com:/home/psergey/mysql-5.0-bug15827-r2

too much memory. Instead, either create the equvalent SEL_TREE manually, or create only two ranges that
strictly include the area to scan
(Note: just to re-iterate: increasing NOT_IN_IGNORE_THRESHOLD will make optimization run slower for big 
IN-lists, but the server will not run out of memory. O(N^2) memory use has been eliminated)

small cleanup fixes in kernel/vm/Configuration

into  perch.ndb.mysql.com:/home/jonas/src/50-work

  Handle early abort of scan, so that resources are correctly freed

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

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

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

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.