in net_printf(), we fill net->last_* variables for the slave SQL thread to know the error.

into mysql.com:/home/mysql_src/mysql-4.0

This does not fix any known bug, but is still a good idea.

into gw.mysql.r18.ru:/usr/home/ram/work/4.0.b2205

into gw.mysql.r18.ru:/usr/home/ram/work/4.0.b2205

into serg.mylan:/usr/home/serg/Abk/mysql-4.0

into mysql.com:/home/mysql_src/mysql-4.0

As I cannot be 100% sure that there won't be issues with some of our exotic platforms
(who knows if the charset of <obscure old OS> will play fair?), I'll send an email to the build guys.
Well, this holds if bk does not crash on binary chars of this cset.

into rhols221.adsl.netsonic.fi:/home/my/bk/mysql-4.0

FLOAT columns".

into gw.mysql.r18.ru:/usr/home/ram/work/4.0.b2631

into mysql.com:/home/mysql_src/mysql-4.0-opt

into mysql.com:/home/mysql_src/mysql-4.0

Dependency fix. We observed that doing any change to class THD in sql_class.h resulted in mysqld going crazy (parsing errors,
query cache errors in query_cache.test). This is because sql_yacc.cc depends on several .h files but those were not listed in
the dependencies of sql_yacc.o. The present patch does fix the issue; but my auto*-expert colleagues may have a better one.

into serg.mylan:/usr/home/serg/Abk/mysql-4.0

(Jani's CS 1.1675 04/01/05 21:45:14 was adapted an aplied).

  Allow FROM or IN in SHOW KEYS, as in other SHOW statements.

  Add GPL comment

into gw.mysql.r18.ru:/usr/home/ram/work/4.0.b5232

into mysql.com:/space/my/mysql-4.0

into mysql.com:/space/my/mysql-4.0-build

  If ALTER TABLE ... DROP FOREIGN KEY ... fails because of a wrong constraint name, return a table handler error number 150 instead of 152; the value 152 was misleading, as it referred to '152 = Cannot delete a parent row', whereas '150 = Foreign key constraint is incorrectly formed' is less misleading

into mysql.com:/M40/mysql-4.0

(backport from 4.1).

into krsna.patg.net:/home/patg/mysql-4.0

  bug #5001, added conditional if to test if port set, then only kill the processes
  for this port, not all processes (in the case of this bug where multiple servers 
  are killed.)
  The change to the 'grep' to make sure mysqld_safe isn't killed was per Serg's
  discovery that mysqld_safe would get killed. 
  In my testing, in killing one of the pids for a running server, the "if test ! -f $pid_file"
  was the case that evaluated as true, so in order to test, I had to comment that block
  out.