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

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

- Fixed tests
- Optimized new code
- Fixed some unlikely core dumps
- Better bug fixes for:
  - #14397 - OPTIMIZE TABLE with an open HANDLER causes a crash
  - #14850 (ERROR 1062 when a quering a view using a Group By on a column that can be null

into  mysql.com:/usr/local/mysql/mysql-5.0

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

into  mysql.com:/usr/local/mysql/mysql-5.0

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

into  mysql.com:/usr/local/mysql/mysql-5.0

parent when we are not the process group leader.

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

when high concurrency": remove HASH::current_record and make it
an external search parameter, so that it can not be the cause of a 
race condition under high concurrent load.
The bug was in a race condition in table_hash_search,
when column_priv_hash.current_record was overwritten simultaneously
by multiple threads, causing the search for a suitable grant record
to fail.
No test case as the bug is repeatable only under concurrent load.

the bug is fixed.

into  mysql.com:/usr/local/mysql/mysql-5.0

  enable view prepared mode during getting metedata for I_S table

into  mysql.com:/home/mydev/mysql-5.0-bug15591

into  mysql.com:/home/mydev/mysql-5.0-bug15591

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

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

If the server is started with --port-open-timeout=# 
retry to bind the TCP port if it fails with EADDRINUSE.
Use the new option in mysql-test-run.sh.

  Backported Windows MAX_INDEXES handling from 5.1

into  devsrv-b.mysql.com:/space/magnus/my50-bug15775_part2

 - Update patch for 5.0 
 - Added common function to be called when 'acl_users' has been modified

into moonbone.local:/work/14583-bug-4.1-mysql

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

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

   - DROP USER command didn't reload the acl_check_hosts cache causing subsequent 
     connect's via TCP to fail randomly.
   - 4.1 version

into  mysql.com:/home/mydev/mysql-5.0-bug5390

into  mysql.com:/home/mydev/mysql-5.0-bug5390

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

When InnoDB compares varchar field in ucs2 with given key using bin collation,
it calls my_strnncollsp_ucs2_bin() to perform comparison.
Because field length was lesser than length of key field should be padded
with trailing spaces in order to get correct result. 
Because  my_strnncollsp_ucs2_bin() was calling my_strnncollp_ucs2_bin(), which
doesn't pads field, wrong comparison result was returned. This results in
wrong result set.

my_strnncollsp_ucs2_bin() now compares fields like my_strnncollsp_ucs2 do,
but using binary collation.