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

into  mysql.com:/home/cps/mysql/trees/5.1/5.1-virgin-debug

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

into  mysql.com:/home/cps/mysql/devel/im/5.0-im-add-error-message

into  mysql.com:/home/jimw/my/mysql-5.1-clean

corrected by Ingo when pushing WL#1563

into  mysql.com:/home/jimw/my/mysql-5.1-clean

into  mysql.com:/home/jimw/my/mysql-5.1-clean

into  mysql.com:/home/jimw/my/mysql-5.1-clean

into  mysql.com:/home/jimw/my/mysql-5.1-clean

into  mysql.com:/home/jimw/my/mysql-5.0-clean

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

  - do not try to create ndb temp tables even if default storage is ndb

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

 - Remove global  MYSQL connection variable

into  snake-hub.snake.net:/src/extern/MySQL/bk/mysql-5.1

into  snake-hub.snake.net:/src/extern/MySQL/bk/mysql-5.0

into  snake-hub.snake.net:/src/extern/MySQL/bk/mysql-5.1

  Tweak --check-upgrade help text.

  Updated version number to 5.1.8

into  snake-hub.snake.net:/src/extern/MySQL/bk/mysql-5.1

into  mysql.com:/usr/home/bar/mysql-5.1-new.16234

into moonbone.local:/work/15706-bug-5.0-mysql

into  mysql.com:/usr/home/bar/mysql-5.1-new.16234

5.1-related fixes

  new file:
  Adding a test case for "Migration tool for 5.1 table name encoding"

  Sorry, forgot to push in the previous changeset.

  WL#3046  Migration tool for 5.1 table-name encoding