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

into mysql.com:/home/psergey/mysql-5.1-look

if we've got a tree of type ALWAYS or MAYBE.

into  mysql.com:/home/kostja/mysql/mysql-5.1-vanilla

Fixes failing sp.test

into  poseidon.ndb.mysql.com:/home/tomas/mysql-5.1-new

into  poseidon.ndb.mysql.com:/home/tomas/mysql-5.1-new

into  mysql.com:/space/pekka/ndb/version/my51

into  poseidon.ndb.mysql.com:/home/tomas/mysql-5.1-new

- test tables use blobs without PK, and was not handled correctly

into  mysql.com:/usr/local/mysql/mysql-5.1-new

fails with --vardir option.

  Fix online ordered index build of varsize table

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

into  rurik.mysql.com:/home/igor/dev/mysql-5.1-0

into mysql.com:/Users/kent/mysql/bk/mysql-5.1-new

  Reintroduced a max build
  Limited testing of 'debug' and 'max' servers
  Berkeley DB only in 'max'

into mysql.com:/Users/kent/mysql/bk/mysql-5.1-new

  Added --restart-cleanup option
drop-on-restart.inc:
  DROP commands to cleanup on restart
  new file
mysqltest.c:
  Added option --include=<sql-file>

We had a number of tests where there were no bugs related to disabling of tests, bugs were fixed, or no clear discription or plan.

into  zim.tangent.org:/home/brian/mysql/dep-5.1

Fixed some threading issues that Guilhem found (and its what I get for copy and pasting from elsewhere without thinking about it). Added depracted messages to BACKUP, RESTORE, and LOAD TABLE FROM MASTER (which doesn't work well). 

into  mysql.com:/space/pekka/ndb/version/my51

"mysqldump" test fails (mysqlimport related, Brian aware), ndb_cache2 ndb_cache_multi2
partition_mgm_err fail (unrelated to my changes), rpl_row_view01 (known crash BUG#17265)

into  mysql.com:/home/mysql_src/mysql-5.1-new

into  mysql.com:/home/mysql_src/mysql-5.1-new; will fix manually sp_head.cc and mysqld.cc later soon.

Fix for BUG#13897 "failure to do SET SQL_MODE=N where N is a number > 31" (the original bug's title isn't the simplest
symptom). sys_var::check_set() was wrong. mysqlbinlog makes use of such SET SQL_MODE=N
(where N is interpreted like if SQL_MODE was a field of type SET), so
this bug affected recovery from binlogs if the server was running with certain SQL_MODE values,
for example the default values on Windows (STRICT_TRANS_TABLES); to work around this bug people
had to edit mysqlbinlog's output.

if the function, invoked in a non-binlogged caller (e.g. SELECT, DO), failed half-way on the master,
slave would stop and complain that error code between him and master mismatch. 
To solve this, when a stored function is invoked in a non-binlogged caller (e.g. SELECT, DO), we binlog the function
call as SELECT instead of as DO (see revision comment of sp_head.cc for more).
And: minor wording change in the help text.
This cset will cause conflicts in 5.1, I'll merge.

Fix for BUG#16559 "Replication Problems with Non transactional tables inside an interrupted trans.":
problem was: when a connection disconnects having an open transaction affecting MyISAM and InnoDB, the ROLLBACK event stored in the binary log
contained a non-zero error code (1053 because of the disconnection), so when slave applied the transaction, slave complained that its ROLLBACK succeeded
(error_code=0) while master's had 1053, so slave stopped. But internally generated binlog events such as this ROLLBACK
should always have 0 as error code, as is true in 4.1 and was accidentally broken in 5.0,
so that there is no false alarm.

into  neptunus.(none):/home/msvensson/mysql/mysql-5.1