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

into  mysql.com:/home/timka/mysql/src/5.0-bug-13832

The cause for the bug is that the priorities of all rules/terminals
that process the FROM clause are not fully specified, and the
parser generator produces a parser that doesn't always parse
the FROM clause so that JOINs are left-associative. As a result
the final join tree produced by the parser is incorrect, which
is the cause for subsequent name resolution to fail.

into  mysql.com:/users/lthalmann/bk/mysql-5.0-enum-logtype

into  mysql.com:/users/lthalmann/bk/mysql-5.0-enum-logtype

into  mysql.com:/users/lthalmann/bk/mysql-5.0-base64

into  mysql.com:/home/alik/Documents/AllProgs/MySQL/devel/5.0-bug13095

into  mysql.com:/home/alik/Documents/AllProgs/MySQL/devel/5.0-bug13095

  - allow CREATE VIEW as well as DROP VIEW to use in prepared statements;
  - fix CREATE VIEW implementation to make it work in prepared statements.

into  krsna.patg.net:/home/patg/mysql-build/mysql-5.0.test2

federated.disabled and instead using disabled.def (per
comments in this commit)

disabled.def:
  disabled federated until bug 14272 is fixed.
.del-federated.disabled~9e4cca59f547174d:
  Delete: mysql-test/t/federated.disabled
federated.disabled:
  New BitKeeper file ``t/federated.disabled'' to disable federated test until
  Bug 14272 is fixed.
  new file

OPTIMIZE TABLE.

into  mysql.com:/users/lthalmann/bk/mysql-5.0-base64

different features, adding numbering to enums reduce the risk that code will
be merged incorrectly.  This particular enum must have fixed values to ensure
that an upgraded server always can read old logs.  I added this, since I 
noticed the incorrect order in the RBR clone.

into  mysql.com:/users/lthalmann/bk/mysql-5.0-hexdump

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

into  mysql.com:/usr/home/pem/bug13941/mysql-5.0

  After merge fix.

into  mysql.com:/usr/home/bar/mysql-5.0.b12371

into  mysql.com:/usr/home/pem/bug13941/mysql-5.0

into  mysql.com:/usr/home/bar/mysql-5.0.b12371

into mysql.com:/home/gluh/MySQL/Bugs/5.0.14089

  select distinct char(column) fails with utf8
ctype_utf8.result, ctype_utf8.test:
  Adding test case
sql_yacc.yy:
  Adding new syntax.
item_strfunc.h:
  Fixing wrong max_length calculation.
  Also, adding CHAR(x USING charset),
  for easier migrating from 4.1 to 5.0,
  according to Monty's suggestion.

                  information_schema is current database
  skip the check of I_S tables if table is derived table

into  mysql.com:/usr/home/bar/mysql-5.0.b12371

into  perch.ndb.mysql.com:/home/jonas/src/mysql-4.1-push

into lmy004.:/work/mysql-5.0-bug12595-4

ESCAPE has length of 1 if specified and sql_mode is NO_BACKSLASH_ESCAPES
or has length of 0 or 1 in every other situation.
(approved patch applied on a up-to-date tree re-commit) 

into  mysql.com:/home/cps/mysql/trees/mysql-5.0

(v.2 with post-review fixes)

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

  Set the version number to 5.0.16

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

ctype_utf8.test, ctype_utf8.result:
  Adding test case.
item.h:
item.cc:
  Adding Item_param::safe_charset_converter

into  mysql.com:/usr/home/bar/mysql-5.0

  Bug#13238 mysqldump and mysqladmin hangs
  Avoid recursion into init_available_charsets.
  Serg's version didn't work for me: I got 
  double mutex locking.
  Pushing this version instead
  (It was approved by Serg anyway)