> source-changes can be massive information overload without filtering,
> and many people are not in a position to filter mail easily.  Other
> might like to recieve one condensed report instead of many many tiny
> messages.  For this reason, I've hacked up a little script to monitor
> source-changes and post a digest of each weeks's amiga and generic-m68k
> changes to the amiga list once a week.  I'll start it next friday, if
> there are no objections. 

Objections?  No way, thanks alot. This will help people that ar not
setup to filter the list (or even handle the raw input.)

> (I still think noting amiga-specific changes in doc/CHANGES or
> arch/amiga/doc/CHANGES would also be a good idea, though).

I will start using a arch/amiga/doc/CHANGES file.  good idea (I didn't
want to make notes specific to the AMIGA like ("massive cleanup" in
the general CHANGES FILE)

> Ty Sarna                 "As you know, Joel, children have always looked

Chris.

------------------------------------------------------------------------------