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

into moonbone.local:/work/14583-bug-5.1-new-mysql

into  neptunus.(none):/home/msvensson/mysql/bug15775_part2/my51-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

Manual merge.

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/stewart/Documents/MySQL/5.1/new

into  xiphis.org:/home/antony/work2/p4-bug15976

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

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

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

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.

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

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

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

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

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

into  pylon.mylan:/home/psergey/mysql-5.1-26dec-merge

into  mysql.com:/home/psergey/mysql-5.1-26dec-merge

into  pylon.mylan:/home/psergey/mysql-5.1-26dec-merge

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

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

  added item_xmlfunc.cc

  Delete: libmysqld/item_xmlfunc.cc

adjust SEL_TREE::keys_map appropriately.

- Added more comments.
- Added a RANGE_OPT_PARAM::remove_jump_scans flag that disables construction of index_merge
  SEL_TREEs that represent unusable conditions like "key1part1<c1 OR key2part2<c2"
- make prune_partitions() function handle the case where range analysis produces a list of 
  index_merge trees (it turned out that this is possible, appropriate test case added).
- Other small fixes.

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