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

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

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

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

not needed by the tescases. This will save test time for those testcases
that does not need cluster, but need a restart, as they dont have to wait
the extra time it would take for cluster to restart. It will also save
time for other testcases, as cluster does not 
need to be contacted for each table to be dropped or created.
Backport from 5.1

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

into  poseidon.ndb.mysql.com:/home/tomas/mysql-5.0

Removed 'delayed' to make the test deterministic (as the bug itself has nothing to do with 'delayed').

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

into  mysql.com:/space/pekka/ndb/version/my50

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

into  mysql.com.:/data/BK/mysql-5.0

into  mysql.com:/space/pekka/ndb/version/my50

into  mysql.com.:/data/BK/mysql-5.0_8461_b

  fix for bug#8461

  BUG 8461 - TRUNCATE returns incorrect result if 2nd argument is negative
  Reason: Both TRUNCATE/ROUND converts INTEGERS to DOUBLE and back to INTEGERS
  Changed the integer routine to work on integers only.
  This bug affects 4.1, 5.0 and 5.1
  Fixing in 4.1 will need to change the routine to handle different types individually.
  5.0 did had different routines for different types already just the INTEGER routine was bad.

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

into  april.(none):/home/svoj/devel/mysql/merge/mysql-5.0

into  april.(none):/home/svoj/devel/mysql/merge/mysql-4.1

into  poseidon.ndb.mysql.com:/home/tomas/mysql-5.0

into  april.(none):/home/svoj/devel/mysql/merge/mysql-4.1

into  april.(none):/home/svoj/devel/mysql/merge/mysql-4.1

into  poseidon.ndb.mysql.com:/home/tomas/mysql-5.0

Bug #17158  	load data infile of char values into table of char with no (PK) fails to load
Bug #17081  	Doing "LOAD DATA INFILE" directly after delete can cause missing data

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

If check_quick_select returns non-empty range then the function cost_group_min_max
cannot return 0 as an estimate of the number of retrieved records.
Yet the function erroneously returned 0 as the estimate in some situations.

into  mysql.com:/extern/mysql/work/bug16303/mysql-5.0

into  mysql.com:/extern/mysql/work/bug16303/mysql-5.0

into  mysql.com:/extern/mysql/work/bug16568/mysql-5.0

into  mysql.com:/space/pekka/ndb/version/my50