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

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

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

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

thd->allow_sum_func was left 'true' after previous statement thus allowing
sum funcs to be present in conditions.

thd->allow_sum_func should be set to 0 for each query and each prepared
statement reinitialization. This is done in lex_start() and 
reset_stmt_for_execute().

into  mysql.com:/home/shuichi/apps/mysql/bk/mysql-5.0b

into serg.mylan:/usr/home/serg/Abk/mysql-5.0-merged

into  mysql.com:/users/lthalmann/bk/mysql-5.0-rollback-comment

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

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

    ndb backup with charsets and simultanious updates
    make sure that backup _dont_ read xfrm data

into  mysql.com:/users/lthalmann/bk/mysql-5.0-rollback-comment

  remove extra ";" after function

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

into  sanja.is.com.ua:/home/bell/mysql/bk/work-owner5-5.0

Fixed a  typo in handler.cc if CSV was built. I also added CSV to the default MAX builds so that more people test it. 

into mysql.com:/home/psergey/mysql-4.1-csc6030-r3

statistics (like 4.0 did) (patch #3, with review #1 & #2 feedback addressed)

into  sanja.is.com.ua:/home/bell/mysql/bk/work-owner5-5.0

WL#2787 (Add view definer/owner to the view definition (.frm) to check privileges on used tables and stored routines when using a VIEW.)
Part 2 postreview fixes.

into moonbone.local:/work/12812-bug-5.0-mysql

  Fixed mistake in fix for bug#12812

into  selena.:H:/MYSQL/src/#12929-mysql-4.1

Not fixed in 4.1 as not critical. Also I'm correcting error checking of multi-UPDATE/DELETE
when it comes to binlogging, to make it consistent with when we rollback the statement.

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

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

The problem was in the way table references are pre-filtered when
resolving a qualified field. When resolving qualified table references
we search recursively in the operands of the join. If there is
natural/using join with a merge view, the first call to find_field_in_table_ref
makes a recursive call to itself with the view as the new table reference
to search for the column. However the view has both nested_join and
join_columns != NULL so it skipped the test whether the view name matches
the field qualifier. As a result the field was found in the view since the
view already has a field with the same name. Thus the field was incorrectly
resolved as the view field.