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

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

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

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

in all cuurently known log files 

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

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

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.

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

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

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/work/my50-work

 - Better control of when to create/remove vardir

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

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

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

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

into  shakedown.(none):/home/jpipes/dev/mysql-5.1-new-maint2

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. 

Don't link mysql_upgrade with mysys

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

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

Problems (appear only under some circumstances): 
  1. we get a reference to a deleted table searching in the 
     thd->handler_tables_hash in the mysql_ha_read().

  2. DBUG_ASSERT(table->file->inited == handler::NONE); assert fails in the
     close_thread_table().

Fix: end open index scans and table scans and remove references to the 
tables from the handler tables hash. After this preparation it is safe 
to close the tables. The close can no longer fail on open index/table 
scans and the closed table will not be used again by handler functions.
                                 

into  polly.local:/home/kaa/src/maint/mysql-5.1-maint

into  polly.local:/home/kaa/src/maint/mysql-5.0-maint

into  polly.local:/tmp/maint/bug22077/my51-bug22077

into  ymer.(none):/usr/local/mysql/tmp/mysql-5.0-gca

into  ymer.(none):/usr/local/mysql/tmp/mysql-5.1-new-maint