buffer overflow and information exposure bugs fixed
  (reported by Stefano Di Paola)
configure.in:
  Changed version to 5.0.17b

and bug #15668: Test 'sp-error' crashes server on Mac OS X.

  incorrect handling of varchar in position/rnd_pos

  Commit for 5.0.17 release clone

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

into mysql.com:/Users/kent/mysql/bk/mysql-5.0-release

  Bug#15629: Increased thread stack for all 64 bit platforms,
  else test case 'sp' and 'call fib(20)' gives stack overrun

into mysql.com:/M50/clone-5.0

into mysql.com:/M50/clone-5.0

Manual merge from 4.1,
extension of the old fix (1.1976 05/12/05 17:57:48 mleich@mysql.com) to two other places.

Fix for bug#12429: Replication tests fail: "Slave_IO_Running" differs:
The value is not important, and it depends on timing. Mask it.

Backport and extension of a fix made by Matthias in 5.0, originally it was
1.1976 05/12/05 17:57:48 mleich@mysql.com

  Ignore columns with unpredictable values.
rpl_relayrotate.result:
  Changed result file to match change in test

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

into mysql.com:/Users/kent/mysql/bk/mysql-5.0-release

  Removed Visual Studio 6 project files, as they are not maintained

into mysql.com:/Users/kent/mysql/bk/mysql-5.0-release

  Removed --text from grep, not portable

into  mysql.com:/usr/local/mysql/mysql-5.0-release

into mysql.com:/Users/kent/mysql/bk/mysql-5.0-release

  Bug#14960, reverted code to make symdir work on Windows
symlink.test:
  Disabled test case on Windows

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

current SP tables locking make impossible view security" with main tree.

into  mysql.com:/home/dlenev/src/mysql-5.0-bg11555-2

into  mysql.com:/home/dlenev/src/mysql-5.0-bg11555-2

impossible view security".

We should not expose names of tables which are explicitly or implicitly (via
routine or trigger) used by view even if we find that they are missing.
So during building of list of prelocked tables for statement we track which
routines (and therefore tables for these routines) are used from views. We
mark elements of LEX::routines set which correspond to routines used in views
by setting Sroutine_hash_entry::belong_to_view member to point to TABLE_LIST
object for topmost view which uses routine. We propagate this mark to all
routines which are used by this routine and which we add to this set. We also
mark tables used by such routine which we add to the list of tables for
prelocking as belonging to this view.

into  mysql.com:/home/timka/mysql/src/5.0-2486