There was a wrong determination of the DB name (witch is 
not always the one in TABLE_LIST because derived tables
may be calculated using temp tables that have their db name
set to "").
The fix determines the database name according to the type 
of table reference, and calls the function check_access() 
with the correct db name so the correct set of grants is found.

into  mysql.com:/home/mydev/mysql-5.0-amerge

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

into  mysql.com:/data0/mysqldev/my/mysql-5.0

into trift2.mysql.com:/M50/mysql-5.0

mysql-test/mysql-test-run.pl  :  Output the usage error if one is given. (Found when fixing bug#20303)

mysql-test/mysql-test-run.pl  :    A fix for bug#20303 "mysql-test-run.pl: Does not recognize -- argument"

into  may.pils.ru:/home/svoj/devel/mysql/BUG19192/mysql-5.0

into  may.pils.ru:/home/svoj/devel/mysql/BUG19192/mysql-5.0

into  mysql.com:/data0/mysqldev/my/mysql-5.0

added 'order by' to avoid result order difference

mark result string using String::mark_as_const()
which prevents CONCAT from reusing it as a buffer
for concatenation result.

fix: return db name for I_S.TABLES(and others) in original letter case.
if mysql starts with lower_case_table_names=1 | 2 then original db name is converted
to lower case(for I_S tables). It happens when we perform add_table_to_list. 
to avoid this we make a copy of original db name and use the copy hereafter.

into  mysql.com:/usr/home/ram/work/4.1.b16546

into  hasky.mysql.fi:/home/anjuta/my/mysql-5.0

into  devsrv-b.mysql.com:/users/msvensson/my50-yassl

 - Better check of required buffer size when processing incoming record headers

into  arthur.local:/home/my/mysql-5.0

into  arthur.local:/home/my/mysql-5.0-clean

Moved the test case to separate non-windows specific file.

into  mysql.com:/data0/mysqldev/my/mysql-5.0

into  hasky.mysql.fi:/home/anjuta/my/mysql-5.0-clean

The problem was missing break; operator.

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

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

            ALTER TABLE crashes
Executing fast alter table (one that doesn't need to copy data)
on tables created by mysql versions prior to 4.0.25 could result
in posterior server crash when accessing these tables.

There was a bug prior to mysql-4.0.25. Number of null fields was
calculated incorrectly. As a result frm and data files gets out of
sync after fast alter table. There is no way to determine by which
mysql version (in 4.0 and 4.1 branches) table was created, thus we
disable fast alter table for all tables created by mysql versions
prior to 5.0 branch.
See BUG#6236.

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

into  perch.ndb.mysql.com:/home/jonas/src/mysql-4.1

into  perch.ndb.mysql.com:/home/jonas/src/mysql-5.0

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

Only check for FN_DEVCHAR in filenames if FN_DEVCHAR is defined.
This allows to use table names with ":" on non windows platforms.
On Windows platform get an error if you use table name that contains FN_DEVCHAR

into  perch.ndb.mysql.com:/home/jonas/src/mysql-4.1

into  perch.ndb.mysql.com:/home/jonas/src/mysql-5.0