Don't use thread priority by default on Mac OS X (bug#18526)

  Build "mysqld_error.h" even if configured --withouth-server (bug#21265)

into  mysql.com:/home/kent/bk/tmp/mysql-5.0-build

  Don't build server when configured --without-server (bug#23973)

into  mysql.com:/home/kent/bk/tmp/mysql-5.0-build

into  mysql.com:/home/kent/bk/tmp/mysql-4.1-build

into  mysql.com:/home/kent/bk/tmp/mysql-5.0-build

  Portable handling of "echo" without newline (bug#24605)
check-cpu:
  In developer script safe to use "printf", not "echo -n"

into  mysql.com:/home/kent/bk/main/mysql-5.0

  Corrected spelling in copyright text
Makefile.am:
  Don't update the files from BitKeeper
Many files:
  Removed "MySQL Finland AB & TCX DataKonsult AB" from copyright header
  Adjusted year(s) in copyright header 
Many files:
  Added GPL copyright text
Removed files:
  Docs/Support/colspec-fix.pl
  Docs/Support/docbook-fixup.pl
  Docs/Support/docbook-prefix.pl
  Docs/Support/docbook-split
  Docs/Support/make-docbook
  Docs/Support/make-makefile
  Docs/Support/test-make-manual
  Docs/Support/test-make-manual-de
  Docs/Support/xwf

into  trift2.:/MySQL/M50/push-5.0

into  trift2.:/MySQL/M50/push-5.0

into  willster.(none):/home/stewart/Documents/MySQL/5.0/ndb-mgm-work

into  poseidon.mysql.com:/home/tomas/mysql-5.0-ndb

into  xiphis.org:/home/antony/work2/mysql-5.0-engines-merge

            repair it

Multi-table delete that is optimized with QUICK_RANGE reports table
corruption.

DELETE statement must not use KEYREAD optimization, and sets
table->no_keyread to 1. This was ignored in QUICK_RANGE optimization.

With this fix QUICK_RANGE optimization honors table->no_keyread
value and does not enable KEYREAD when it is requested.

  Changed header to GPL version 2 only

into  trift2.:/MySQL/M50/push-5.0

into  chilla.local:/home/mydev/mysql-5.0-axmrg

into  trift2.:/MySQL/M50/push-5.0

into  bk-internal.mysql.com:/data0/bk/mysql-5.0-build

into  chilla.local:/home/mydev/mysql-5.0-axmrg

Compiler warnings due to non-matching conversion
specifications in format strings in DBUG_PRINT calls,
due to non-used parameters (in non-debug mode), and
due to seemingly uninitialized variables.

Initialized variables, declared parameters unused, and
casted DBUG_PRINT arguments to get rid of warnings.

Compiler warnings due to non-matching conversion
specifications in format strings in DBUG_PRINT calls.

Fixed DBUG_PRINT format specifiactions.

into  trift2.:/MySQL/M50/clone-5.0

into  trift2.:/MySQL/M50/clone-5.0

into  trift2.:/MySQL/M50/push-5.0

into  kahlann.erinye.com:/home/df/mysql/build/mysql-5.0-release

into  kahlann.erinye.com:/home/df/mysql/build/mysql-5.0-release

into  siva.hindu.god:/usr/home/tim/m/bk/50-build

into  siva.hindu.god:/usr/home/tim/m/bk/50-build

into  siva.hindu.god:/usr/home/tim/m/bk/50-release

more similar to my_strtod() (and maybe even a bit faster due
to less floating point divisions).

This should at least partially fix Bug #23260 for DECIMALs
with a moderate number of total digits.

InnoDB timeout behavior (Bug #24200)

Handling of large signed/unsigned values was not consistent, so some string functions could return bogus results.
The current fix is to simply patch up the val_str() methods for those string items.
It would be good clean this code up in general, to make similar problems much harder to make.  This is left as an exercise for the reader.