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-4.1-maint

 - Better control of when to create/remove vardir

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

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

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  neptunus.(none):/home/msvensson/mysql/mysql-4.1-maint

traces in Valgrind (broken libc6-dbg).
Installing libc6-dbg on Debian will still provide proper bactraces, even
without setting LD_LIBRARY_PATH explicitly.

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

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

And it's not an "opt"

into  mysql.com:/usr/home/ram/work/bug21789/my41-bug21789

into  mysql.com:/usr/home/ram/work/bug22029/my41-bug22029

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

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

$MYSQLTEST_VARDIR, for usage of vardir=e:/var<nnn> on windows

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

Update usage description

into  example.com:/work/bug24219/my41

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

into  mysql.com:/usr/home/ram/work/bug23653/my41-bug23653

There was an improper order of doing chained operations.

To the documentor: ENABLE|DISABLE KEYS combined with RENAME TO, and no other
ALTER TABLE clause, leads to server crash independent of the presence of
indices and data in the table.

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