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

into  mysql.com:/home/mysql_src/mysql-5.0-release

Indeed now that stored procedures CALL is not binlogged, but instead the invoked substatements are,
the restrictions applied by log-bin-trust-routine-creators=0 are superfluous for procedures.
They still need to apply to functions where function calls are written to the binlog (for example as "DO myfunc(3)").
We rename the variable to log-bin-trust-function-creators but allow the old name until some future version (and issue a warning if old name is used).

into  mysql.com:/home/mysql_src/mysql-5.0-release

"Item_date_add_interval needs to have the int_type member as Public".
As explained in the bug report, this change is is to help http://search.cpan.org/~philips/DBIx-MyParse-0.20/
So please keep those members public.

(Currently, affects only BSD with Linuxthreads)

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

gives MYSQL_DATA_TRUNCATED"

  Corrected the syntax for the current_user() case.
  (It's "definer = current_user[()]", not just "current_user[()]".)

into mysql.com:/M50/mysql-5.0

into mysql.com:/home/psergey/mysql-5.0-nov08-push

into mysql.com:/M50/mysql-5.0

into mysql.com:/home/psergey/mysql-5.0-nov08-push

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

into mysql.com:/home/psergey/mysql-5.0-nov08-push

into mysql.com:/home/psergey/mysql-5.0-oct08-push

into production.mysql.com:/usersnfs/istruewing/autopush/mysql-5.0

into mysql.com:/home/psergey/mysql-4.1-nov08-push

into mysql.com:/home/psergey/mysql-4.1-nov08-push

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

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

into mysql.com:/M50/mysql-5.0

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

Replace the full socket path name, not just a directory component. bug#14720

Initialized 'ptr' for a newly instantiated varstring field.
This is required by INSERT DELAYED.

No test case. This is a migration issue. There are two shell
scripts attached to the bug report. They can be used for testing.

test "length" first (otherwise when "length" is 0, the *from invalid access still triggers a Valgrind warning).
I wrote to the Valgrind authors in case this is something fixable in Valgrind (normally the
decision to issue a warning is based on the simulated CPU condition code, which should not be undefined here).

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

when calculating table->null_fields.

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