Kill libc-ports?

[Carlos O'Donell]

On 09/06/2013 08:38 AM, Joseph S. Myers wrote:
> My suggestion is that libc-ports would be for all architectures (where 
> architecture maintainer action is needed) rather than just for some 
> subset.

I like this idea.

I suggest:

* Leave libc-alpha as the main high-volume development list.
  - Discuss all development on this list for all machines.
  - Thomas reminded me of all the reasons why we shouldn't just
    arbitrarily change mailing list names.
  - You can still tag your emails if you want with [all-arch]
    or [s390][ppc], but subscribing to another mailing list is
    just easier for filtering.

* Use libc-ports as the low-volume cross-all-ports change notification list.
  - Joseph makes a good point about high-volume on libc-alpha and a need
    for a developer notification list.

Comments?

Cheers,
Carlos.