Fix for BIT(X) field as string

into mysql.com:/home/my/mysql-4.1

  Added a test case for bug #7769.
item_sum.h:
  Fixed bug #7769: a crash for queries with group_concat and
  having when the query table was empty.
  The bug was due an unsafe dereferencing.

into serg.mylan:/usr/home/serg/Abk/mysql-4.1

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

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

into mysql.com:/space/my/mysql-4.1

compatible with 4.1.9

  --with-cluster are provided. Yes, this sounds like a contradiction -
  enabling debugging in NBD enables code parts that may still reveal 
  portability issues when compiled with non-gcc compilers. (request by TomasU)

into gw.mysql.r18.ru:/usr/home/ram/work/5.0

pack_length_in_rec() func has been introduced.

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

into mysql.com:/home/dlenev/src/mysql-4.1-dtbug

This completes the patch for fast TRUNCATE TABLE.

into hundin.mysql.fi:/home/marko/j/mysql-5.0

additional fix for cp932 and eucjpms, recently implemented by
Shuichi.

into mysql.com:/home/dlenev/src/mysql-4.1-dtbug

into arthur.local:/my/mysql-5.0-clean

into mysql.com:/home/my/mysql-4.1

The bug was that if you have two TL_WRITE_DELAYED at the same time,
mi_lock_databases() could be done in the wrong order and we could write the wrong header to the MyISAM index file.

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

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

  "Add a comment why data modifying SQL statements MUST always use a locking read in tables that they read: otherwise the execution is not serializable, and in many cases is not well-defined; we also merged the associated bug fix from 4.1"

it has been specified. (Bug #7347)

into arthur.local:/my/mysql-5.0-clean

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