into  mysql.com:/home/alik/Documents/AllProgs/MySQL/devel/5.0-rt

into  mysql.com:/home/alik/Documents/AllProgs/MySQL/devel/5.0-rt

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

Reduce code

 - Use tmp sh file both in system and popen 

Use system inestad of exec

into  zippy.(none):/home/cmiller/work/mysql/mysql-5.0.19-tbr

into  zippy.(none):/home/cmiller/work/mysql/mysql-5.0.19-tbr

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

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

into  mysql.com:/usr/home/bar/mysql-5.0

into mysql.com:/home/gluh/MySQL/Merge/5.0

into  devsrv-b.mysql.com:/space/magnus/bug17377/my50-bug17377

into mysql.com:/home/gluh/MySQL/Merge/5.0

into  devsrv-b.mysql.com:/space/magnus/bug17377/my50-bug17377

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

into  mysql.com:/usr/home/bar/mysql-4.1.b15949

  Check if the host of table hash record exactly matches host from GRANT command

into  mysql.com:/home/timka/mysql/src/5.0-bug-15229

  calculate Item_func_format::max_length using charset->mbmaxlen

into  mysql.com:/opt/local/work/mysql-5.0-root

into  mysql.com:/opt/local/work/mysql-5.0-root

into  mysql.com:/opt/local/work/mysql-5.0-root

it breaks binary compatibility. The patch will be left intact
in 5.1.

into  mysql.com:/home/dlenev/src/mysql-5.0-merges

into  mysql.com:/opt/local/work/mysql-4.1-root

qualified subject table" which was introduced during work on bug #13525
"Rename table does not keep info of triggers".

The bug was caused by the fact that during reconstruction of CREATE TRIGGER
statement stored in .TRG file which happened during RENAME TABLE we damaged
trigger definition in case when it contained fully qualified name of subject
table (see comment for sql_yacc.yy for more info).

into  mysql.com:/home/mydev/mysql-4.1-bug11527