public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Stuart Herbert" <stuart.herbert@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] gentoo-dev-announce list
Date: Tue, 27 Jun 2006 08:32:20 +0100	[thread overview]
Message-ID: <b38c6f4c0606270032u2dac3d37mfd82473704c2f7c7@mail.gmail.com> (raw)
In-Reply-To: <449DFDD1.1090506@gentoo.org>

On 6/25/06, Donnie Berkholz <spyderous@gentoo.org> wrote:
> This topic has come up in the past, and I'd like to revive it once
> again. The gentoo-dev list has gotten a lower and lower signal to noise
> ratio over the past year or two, and it's difficult to dig out the stuff
> that's truly required reading.

What's noise to you is signal to others.  For example, my interest is
servers, so all of your X.org posts are mostly noise to me, but to
others it's essential signal.  Same goes for the scientific re-org
recently discussed.  And I'm sure the same goes for PHP & webapp
stuff.

> I propose that all need-to-know announcements and decisions be posted to
> a separate, moderated (or restricted posting) gentoo-dev-announce list
> to ensure that no developers lose track of what really matters.

I think a -dev-announce ML is a good idea, with reply-to set to -dev.
But I also think you're over-exaggerating the situation by a long way,
sorry.

Best regards,
Stu
--
PS: If anyone needs anything posting on -announce, I'm one of the
people you can bribe :)
-- 
gentoo-dev@gentoo.org mailing list



  parent reply	other threads:[~2006-06-27  7:37 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-25  3:06 [gentoo-dev] gentoo-dev-announce list Donnie Berkholz
2006-06-25  3:30 ` Lance Albertson
2006-06-25  3:54   ` Marius Mauch
2006-06-25  4:01     ` Lance Albertson
2006-06-26 18:47     ` Chris Gianelloni
2006-06-25  5:35   ` Donnie Berkholz
2006-06-25  3:32 ` Ned Ludd
2006-06-25  5:38   ` Donnie Berkholz
2006-06-26 19:10     ` Chris Gianelloni
2006-06-26 20:10       ` Donnie Berkholz
2006-06-26 23:36         ` Lance Albertson
2006-06-27 11:29           ` Simon Stelling
2006-06-28  1:56           ` Ned Ludd
2006-06-27 11:57         ` Chris Gianelloni
     [not found] ` <20060625190022.GE13449@elladan.wh-og.hs-niederrhein.de>
2006-06-25 22:18   ` Donnie Berkholz
2006-06-27  7:32 ` Stuart Herbert [this message]
2006-06-27 11:20   ` Enrico Weigelt
2006-06-27 11:29     ` Stuart Herbert
2006-06-27 11:24   ` Simon Stelling
2006-06-27 11:32     ` Stuart Herbert
2006-06-27 16:16   ` Donnie Berkholz
2006-07-01 18:00     ` [gentoo-dev] " Ryan Hill
2006-07-01 20:01       ` Donnie Berkholz
  -- strict thread matches above, loose matches on Subject: below --
2007-06-21 21:09 [gentoo-dev] " Donnie Berkholz
2007-06-21 21:16 ` Mike Doty
2007-06-21 21:33   ` Jim Ramsay
2007-06-21 21:37     ` Mike Doty
2007-06-21 21:55       ` Jim Ramsay
2007-06-21 22:10       ` Chris Gianelloni
2007-06-21 21:38 ` Joe Peterson
2007-06-22  1:34 ` Kumba
2007-06-22  2:06 ` Seemant Kulleen
2007-06-22  9:24   ` Thomas Raschbacher (Gentoo)
2007-06-22  3:02 ` Daniel Ostrow
2007-06-22 10:59   ` Ferris McCormick
2007-06-22 11:26 ` Wernfried Haas
2007-06-23  8:12   ` Alec Warner
2007-06-24 12:46     ` Vlastimil Babka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b38c6f4c0606270032u2dac3d37mfd82473704c2f7c7@mail.gmail.com \
    --to=stuart.herbert@gmail.com \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox