\W enables show warnings, \w disables; Showing message while interactive when using the \w and \W commands; using strmov instead of my_strdup; removed case for options, my_getopt does it

into kriem.kemuri.org:/home/geert/MySQL/mysql-5.0

  Add a big fat warning for future programmers that MySQL may call ::store_lock() also with lock 'type' TL_IGNORE; my ignorance of this caused bug 9670

into hundin.mysql.fi:/home/heikki/mysql-5.0

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

  Added a test in connection with the fix for
  bug #6106.
view.result, view.test:
  Added test cases for bugs #6106/6107.
sql_show.cc:
  The addition of the case for items of the type REF_ITEM in the
  function uses_only_table_name_fields became necessary after
  the fix for bug #6106.
sql_base.cc:
  The problem was due to the fact that two different column
  references were glued together though one of them belonged to
  a subquery while another to an outer query. This caused
  eventually a wrong calculation of values for the used_tables
  attribute.

into mysql.com:/home/cps/mysql/trees/mysql-5.0

into mysql.com:/home/jimw/my/mysql-5.0-clean

  Fix part of bug #9670: if MySQL calls ::store_lock with TL_IGNORE, do not change prebuilt->select_lock_type; this fix may heal the assertion failures reported in UPDATE and multi-table UPDATE; it is not clear if this fixes the problems in OPTIMIZE TABLE

into mysql.com:/usr/local/home/marty/MySQL/mysql-5.0

into mysql.com:/usr/local/home/marty/MySQL/mysql-5.0

into mysql.com:/home/pem/work/mysql-5.0

into mysql.com:/home/jimw/my/mysql-4.1-clean

                causes system crash.

  At the shutdown, write the latest lsn only to the first pages of the ibdata files of the system tablespace, NOT to the .ibd files; writing to tens of thousands .ibd files can take minutes

  Fix the patch of Jan to optimize next-key locking in searches of type 'primary key >= some value'

into hundin.mysql.fi:/home/heikki/mysql-4.1

into kriem.kemuri.org:/home/geert/MySQL/mysql-5.0

  Do not test the value of err if the lock operation was skipped because innodb_logs_unsafe_for_binlog was TRUE; though this did not cause any bugs visible to the user, because err is inited to DB_SUCCESS at the start of the function row_search_for_mysql()

not produce phantom (bug #9354).

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

    correct result after bugfix
sql/sql_class.cc
    initialize net.query_cache_query

into mysql.com:/home/pem/work/mysql-5.0

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