into  zim.(none):/home/brian/mysql/archive-newformat-5.1

2) We now store shortest and longest row information.
3) archive_reader can now check and backup files (even if they are hot)
4) We now record longest and shortest row information for stats. 

into  bk-internal.mysql.com:/data0/bk/mysql-5.1-arch

into  mysql.com:/home/kent/bk/tmp2/mysql-5.1-build

into  mysql.com:/home/kent/bk/tmp2/mysql-5.1-build

into  trift2.:/MySQL/M51/tmp-5.1

into  bk-internal.mysql.com:/data0/bk/mysql-5.1-arch

REAL_PATH was rewritten for DATA DIRECTORY (doesn't get calculated for each table open, and won't be calculted more then once now).
Windows warnings cleanup.

I am still get a weird warning about file descriptors closed multiple times.

into  zim.(none):/home/brian/mysql/archive-format-5.1

into  bodhi.local:/opt/local/work/mysql-5.1-runtime

into  weblab.(none):/home/marcsql/TREE/mysql-5.1-22687

into  mysql.com:/home/gluh/MySQL/Merge/5.1-opt

into  mysql.com:/home/gluh/MySQL/Merge/5.1-opt

into  mysql.com:/home/gluh/MySQL/Merge/5.1-opt

ENUMs weren't allowed to have character 0xff, a perfectly good
character in some locales.  This was circumvented by mapping 0xff in
ENUMs to ',', thereby prevent actual commas from being used. Now if
0xff makes an appearance, we find a character not used in the enum and
use that as a separator. If no such character exists, we throw an
error.

Any solution would have broken some sort of existing behaviour. This
solution should serve both fractions (those with 0xff and those with
',' in their enums), but WILL REQUIRE A DUMP/RESTORE CYCLE FROM THOSE
WITH 0xff IN THEIR ENUMS. :-/ That is, mysqldump with their current
server, and restore when upgrading to one with this patch.

into  mysql.com:/home/gluh/MySQL/Merge/5.0

into  mysql.com:/home/gluh/MySQL/Merge/5.0

fixed valgrind error
fixed indentation

into  tiger.mmj.dk:/Users/mmj/bktrees/mysql-5.1-build

According to some internal communication, these two functions are place
holders for future enhancements. Because they use a variable number of
parameters, the implementation defined a reserved keyword for them in the
parser grammar.

Unfortunately, doing so creates a bug similar to Bug 21114 reported for the
function FORMAT.

In the 5.1 code base, due to improvements in the code implemented with bug
21114, having a reserved keyword for functions with a variable number of
arguments is not needed any more by the implementation.

As a result, this fix removes the place-holder implementation, and removes
the unnecessary reserved keywords. Should the functions UNIQUE_USERS and
GROUP_UNIQUE_USERS be finally implemented in a later release, the
implementation should sub class Create_native_func in sql/item_create.cc.
For example, see the class Create_func_concat.

into  siva.hindu.god:/home/tsmith/m/bk/mysql-5.1-build

into  trift2.:/MySQL/M51/push-5.1

into  trift2.:/MySQL/M51/push-5.1

into  bodhi.local:/opt/local/work/mysql-5.1-runtime

into  trift2.:/MySQL/M51/push-5.1

into  rakia.gmz:/home/kgeorge/mysql/autopush/B25106-5.0-opt

           aliases ignored
When a column reference to a column in JOIN USING is resolved and a new 
Item is created for this column the user defined name was lost.
This fix preserves the alias by setting the name of the new Item to the
original alias.

into  weblab.(none):/home/marcsql/TREE/mysql-5.1-25183

into  mysql.com:/home/gluh/MySQL/Merge/5.1-opt

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

  Reverted change for bug#13859, applied smaller patch from Marko

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

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

into  mysql.com:/d2/hf/mr10/my51-mr10

into  mysql.com:/d2/hf/mr10/my50-mr10