into mysql.com:/Users/kent/mysql/bk/mysql-4.1

  Enable build with CXX=gcc and gcc version 4

into mysql.com:/Users/kent/mysql/bk/mysql-4.1

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

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

Using 8 bytes for data pointer does not work at least on
all computers. The result may become 0 or negative number.
(mysqld, myisamchk)
 

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

  Added test cases for bug #11469.
item_strfunc.h:
  Fixed bug #11469: wrong implementation of the not_null_tables
  method for CONCAT_WS.

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

(IN() remove NULL rows only for tables from first argument (value which we looking for in IN() list) but not for tables from IN() list)
Also it will be better change Item::not_null_tables() to prohibit this optimisation by default for new created items in 5.0 or 5.1.

into hundin.mysql.fi:/home/marko/mysql-4.1

into rurik.mysql.com:/home/igor/mysql-4.1

This fixed a failure of insert_update.test on some platforms

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

into rurik.mysql.com:/home/igor/mysql-4.1

  Added a test case for bug #11414.
sql_select.cc:
  Fixed bug #11414: crash on Windows with some simple
  GROUP BY queries.
  It happened to an allocation of an array containing
  0 Copy_field elements in setup_copy_fields.
  The bug had been already fixed in 5.0.

  Fixing tests accordingly.
ctype-ucs2.c:
  The same fix for UCS2.
ctype-utf8.c:
  Bug #9557
  MyISAM utf8 table crash
  The problem was that my_strnncollsp_xxx could
  return big value in the range 0..0xffff.
  for some constant pairs it could return 32738,
  which is defined as MI_FOUND_WRONG_KEY in
  myisamdef.h. As a result, table considered to
  be crashed. 
  Fix to return -1,0 or 1.

  Bug#11009, some more cleanup of unneded files from bootstrap

  Bug#9873, reenabled --without-man option to work

  Enable build with CXX=gcc and gcc version 4

  Corrected quoting of string "pro-nt"

  Added missing `;' to DBUG_RETURN()

into mysql.com:/my/mysql-4.1

Fixes while reviewing new pushed code
NULL as argument to encrypt/decrypt should return NULL without a warning

up CREATE TABLE in innodb_file_per_table=1 mode.

into mysql.com:/my/mysql-4.1

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

#9728  'Decreased functionality in "on duplicate key update
#8147  'a column proclaimed ambigous in INSERT ... SELECT .. ON DUPLICATE'

This ensures fields are uniquely qualified and also that one can't update other tables in the ON DUPLICATE KEY UPDATE part

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

into rurik.mysql.com:/home/igor/mysql-4.1

Moved the key statistics update to info().
The table is not locked in open(). This made wrong stats possible.

No test case for the test suite.
This happens only with heavy concurrency.
A test script is added to the bug report.