On Mon, 2006-06-26 at 17:36 -0600, Lance Albertson wrote: > Donnie Berkholz wrote: > > > Agree, but with the caveat that devs must still be at least subscribed > > to -core even if they choose not to read it. This way, you could have a > > -dev-announce that also refers to something private on -core if need be. > > > >> Now, do we really need it to be -core-announce? Not really. In fact, > >> at one point we'd come up with both a -core-announce and a > >> -dev-announce, with -core-announce being for more sensitive information. > > > > I'm having a tough time thinking of sensitive information that all devs > > must know about (i.e., that would qualify for -core-announce). >
> I'd rather not create a -core-announce. The amount of times those types > of things come up on the list are rare. It would be easier to have an > standard subject heading (maybe ANNOUNCEMENT:) that people can use in > their filters. If devs start abusing it, then we'll vote them off the > island :) Simple, Effective.. I like it.. -- Ned Ludd <[EMAIL PROTECTED]> Gentoo Linux -- gentoo-dev@gentoo.org mailing list
