Incomplete ALTER TABLE breaks MERGE compatibility
  Fix implicit NOT NULL not set on ALTER of PK columns

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

This is the second of three changesets. It contains the pure bug fix.
It also contains the second after-review fixes.
The problem was that with gcc on x86, shifts are done modulo word size. 
'value' is 32 bits wide and shifting it by 32 bits is a no-op.
This was triggered by an evil distribution of character incidences. 
A distribution of 2917027827 characters made of 202 distinct values led to
34 occurrences of 32-bit Huffman codes.
This might have been the first time ever that write_bits() had to write
32-bit values. Since it can be expected that one day even 32 bits might
be insufficient, the third changeset suggests to enlarge some variables
to 64 bits.

Added protection against global read lock while creating and
initializing a delayed insert handler.
Allowed to ignore a global read lock when locking the table
inside the delayed insert handler.
Added some minor improvements.

  while testing changes to the mysql-copyright scripts

- fixed copyright header and removed obsolete comments about how to
  build the manual using texinfo
- added an "install-data-hook" to install the mysql.info info page.
  This seems to be the only way to install info pages, if they are not
  built from texinfo sources directly.

  (it's already in EXTRA_DIST of the toplevel Makefile.am)

  already (and that's the Makefile that acutally creates it)

don't set lex->lock_option=TL_READ in the parser for SELECT

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

bug#8151

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

set_bit replaced with internal_set_bit,
clear_bit replaced with internal_clear_bit.

- fixed a date for a changelog entry  in the RPM spec file (s/Mar/Apr/) - RPM complains about wrongly
  ordered entries.

  references to the .texi file and the build targets that depend on manual.texi as the input file.
- added COPYING as a regular file instead of creating it during the build. This ensures that it's part
  of the sources when pulling from BK (it used to be extracted from the manual)
- Removed a lot of cruft and unused/obsolete stuff from the Docs directory (e.g. Flags, Images)
- added a dummy mysql.info placeholder file (the info file is still used as the source to extract
  various text files during the build). It will be replaced with a "real" file during the Bootstrap
  process to create the official source distribution - the placeholder just satisfies build dependencies.

function".

We should not cache queries using CURRENT_USER() function as we do it
for some other functions, e.g. USER() function.

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

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

into mysql.com:/home/dlenev/src/mysql-4.0-bg8894

sql/sql_table.cc: print an error with a function that respects width modifiers (%.64s)

checked with --auto-repair mode returned an error (such
as being a merge table). (Bug #9492)

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

  Added option --with-big-tables

the current way of passing '-DBIG_TABLES' to the compilers.

This is needed even in 4.0, as 'Do-compile-all' must use this new approach for
all "max" builds in 4.0, 4.1, and up.

Fixed Field_timestamp::val_int() so now it works correctly in --new mode
(or for TIMESTAMP(19) columns). 
Also removed unused Field_timestamp::fill_and_store() method.

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

  If MySQL wrote to its binlog, but for some reason trx->update_undo and trx->insert_undo were NULL in InnoDB, then trx->commit_lsn was garbage, and InnoDB could assert in the log flush of trx_commit_complete_for_mysql() (Bug #9277)

into frost.snake.net:/Volumes/frost2/MySQL/bk/mysql-4.0

into quadxeon.mysql.com:/nfstmp1/guilhem/mysql-4.0-4xeon

When we come to create these, they may already exist and it's necessary to delete these old, useless copies.