splitting this list

[Ben Elliston]

OK, now that I have donned my asbestos ninja costume --

What do folks think about trying to alleviate the increasingly heavy
volume on this list into something more manageable?  I was thinking
that, for example, the most common target architectures (i386, alpha,
sparc, ppc) could get their own "gcc-<foo>" list for target specific
discussions.  Any architecture without a dedicated list could default
to the gcc@ list and, if an architecture got sufficiently noisy, a
target-specific list could be created for it at that stage.

It might also help to have separated lists for documentation/WWW
changes and for testing.  Comments?

Ben