ANNOUNCEMENT and WARNING: ben-mule-21-5 is now offially merged in.

For an [admittedly incomplete] list of changes, see new file
CHANGES-ben-mule in the top level.
There is also some other information in README.ben-mule-21-5 and
TODO.ben-mule-21-5, although it's not very well organized; and there's
information in various source files, usually near the top -- e.g. in
src/config.h.in and in src/intl-encap-win32.c.

I have tested it fairly thoroughly on Windows and Cygwin+XFree86 [which
catches most Unix problems, since I can run under X Windows], but there
undoubtedly will be problems on other platforms and in parts of the file
that didn't get tested and normally aren't hit except by certain people.

NOTE: There are still some test suite failures.  No crashes, though, and
none of the test suite failures are very important at all except
possibly that the md5 code seems to not be working too well right now. 
In fact, many of the failures have to do with problems in the test suite
itself rather than in the actual code, and I'll fix all these problems
within a day.

For the meantime, I'd like to see everybody test it out on normal
operations and see what problems come up.  I'm sure there are going to
be a fair number, and consequently a large amount of instability in the
next few days, which should straighten itself out again by the end of
this week, if not sooner.

All comments should be sent to [email protected] -- when sending to a
mailing list, make sure to Cc: [email protected].  I see email much faster
when it has my email address in the headers than when it doesn't.  Also,
clearly tag your bug report, e.g. by adding [MERGED-BEN-MULE] at the
beginning of the subject.  That way, any reports that somehow or other
don't get sent directly to me can still be easily filtered out.

Also, pre- and post- tags exist, noting the state of the trunk just
before and just after the checkin:

pre-ben-mule-21-5-merge-in
post-ben-mule-21-5-merge-in



Enjoy!

ben