into dl145c.mysql.com:/home/ndbdev/tomas/mysql-5.0

into dl145c.mysql.com:/home/ndbdev/tomas/mysql-5.0

  fixed 64bit bug in lenght store/retrive in cache

  Add one more step to the patching instructions.
lexyy.c:
  Fix a Win64 type conversion warning

Bug#8367 "low log doesn't gives complete information about prepared 
statements"
Implement status variables for prepared statements commands (a port of
the patch by Andrey Hristov).
See details in comments to the changed files.
No test case as there is no way to test slow log/general log in 
mysqltest.

ALTER, OPTIMIZE and ANALYZE statements".
In 4.1 we disabled logging of slow admin statements. The fix adds an 
option to enable it back.
No test case (slow log is not tested in the test suite), but tested
manually.
+ post-review fixes (word police mainly).

  Correction after merge of fix for bug #8614.

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

  Added a test case for bug #8614.
sql_select.cc:
  Fixed bug #8614.
  SELECT DISTINCT ... GROUP BY 'const' must be equivalent to
  SELECT ... GROUP BY 'const'.

into mysql.com:/opt/local/work/mysql-5.0-root

into three.local.lan:/home/matthias/Arbeit/mysql-5.0/src-B

into mysql.com:/home/timka/mysql/src/5.0-dbg

Exclude the query that generates warning from PS tests, due to extra warning
under PS.

Removed SHOW BINLOG EVENTS in test case for ps-protocol and row-based replication

into three.local.lan:/home/matthias/Arbeit/mysql-5.0/src-B

into mysql.com:/M50/mysql-5.0

into mysql.com:/opt/local/work/mysql-5.0-root

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

into mysql.com:/home/matthias/Arbeit/mysql-5.0/src-B

into mysql.com:/home/svoj/devel/mysql/yassl-mysql-5.0

Merge with latest yaSSL.

into mysql.com:/home/stewart/Documents/MySQL/4.1/bug11132

into mysql.com:/home/stewart/Documents/MySQL/5.0/bug11132

into three.local.lan:/home/matthias/Arbeit/mysql-5.0/src-B

into mysql.com:/opt/local/work/mysql-5.0-root

into mysql.com:/home/gluh/MySQL/Merge/5.0

  added ability to do SHOW CREATE DATABASE `information_schema`

This fixes the problem in 5.0 in the correct way.

The previous patch (for 4.1) is only valid for 4.1 and is done at the right time
for 4.1.

into mysql.com:/usr/home/ram/work/mysql-5.0