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

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

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

into  zippy.cornsilk.net:/home/cmiller/work/mysql/mysql-5.0-maint

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

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

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

in all cuurently known log files 

After that it will by default use log tables. That setting can be overruled
by adding a -master.opt file like mysql_client_test has.

  If using \$(srcdir)/mysql.info in action, use same in rule.

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

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

if that is same as opt_mem it can be removed

with the function where vardir's are created

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

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

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

 - Better control of when to create/remove vardir

into  mysql.com:/usr/home/ram/work/bug21587/my50-bug21587

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

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

And if var/ has been created, it will be recreated later so the logs
from "mtr_kill_leftovers" will be lost anyway  

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

And if var/ has been created, it will be recreated later so the logs will
be lost  

mysql-test-run.pl:
    Removed "use diagnostics", reduces Perl speed significantly. Can be
    enabled with "perl -Mdiagnostics mysql-test-run.pl".
mtr_report.pl:
   Don't try output "skipped" comment if there is none (bug#24471)

into  mysql.com:/home/kent/bk/mysql-5.0-build

into  mysql.com:/home/kent/bk/mysql-5.0-merge

into  mysql.com:/home/kent/bk/mysql-4.1-merge

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

  Reenabled build outside source tree

into  shakedown.(none):/home/jpipes/dev/mysql-5.0-maint

master_port after a "change master" will be set to the compiled in default value
i.e not always the same as what the master report as it's port number.