Missed one place in DO-UNARY-BYTE-BASH to adjust the call to END-MASK
to use a bit offset instead of a byte offset.  This affects anything
that was using DO-UNARY-BYTE-BASH, including REPLACE.

prints.

code/bit-bash.lisp::
 Add {{{BYTE-BASH-COPY}}} for copying bytes

code/exports.lisp::
 Add {{{BYTE-BASH-COPY}}}

compiler/generic/vm-fndb.lisp::
 Add {{{BYTE-BASH-COPY}}}

compiler/generic/vm-tran.lisp::
 Call {{{BYTE-BASH-COPY}}} in the deftransform for {{{REPLACE}}}.

entries with just the file path, removing the revision number, date,
author and state.  The actual information is now computed during
compilation and stored in the fasl itself.  (See ticket:48.)

boot-2010-02-1 as the bootstrap file.  You should probably also use
the new -P option for build.sh to generate and update the po files
while building.

unicode-utf16-extfmt-2009-06-11.

o Change MAX-BITS to #xffffffff.  This fixes (works around) the issue
  reported by Walter Pelissero, reported on cmucl-help, 2008-01-09.
  We will still have problems for sufficiently long strings.

boot-2007-12-1.lisp:
o Boot file to use for the above change.

only needed to read one word of the source to compute the rightmost dst
word.  We were reading two words which made load seg-fault because next src
word was on a different page (that wasn't mapped in).

to load the last src word or not backwards, so we didn't load it when we
needed it.  (And potentially read one too many words when we didn't need
it.)

Commented out all the bit-bash-mumbles, 'cause the compiler can't deal with 'em yet.
Added interpreter stubs for the four copy functions.

special purpose unsigned-byte 32 functions.  Replaced merge-bits with a
function that gets translated into spiffy code.