From owner-freebsd-stable  Mon Jun 10 11:45:44 1996
Return-Path: owner-stable
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id LAA02102
          for stable-outgoing; Mon, 10 Jun 1996 11:45:44 -0700 (PDT)
Received: from mailhub.cts.com (mailhub.cts.com [192.188.72.25])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id LAA02096
          for <stable@freebsd.org>; Mon, 10 Jun 1996 11:45:42 -0700 (PDT)
Received: from io.cts.com(really [198.68.174.34]) by mailhub.cts.com
	via smail with esmtp
	id <m0uTBy9-000V4OC@mailhub.cts.com>
	for <stable@freebsd.org>; Mon, 10 Jun 96 11:45:41 -0700 (PDT)
	(Smail-3.1.92 1996-Mar-19 #3 built 1996-Apr-21)
Received: (from root@localhost) by io.cts.com (8.7.5/8.6.9) id LAA01201; Mon, 10 Jun 1996 11:45:44 -0700 (PDT)
From: Morgan Davis <root@io.cts.com>
Message-Id: <199606101845.LAA01201@io.cts.com>
Subject: Re: mail overload.
To: john@ulantris.infinop.com (John A. Booth)
Date: Mon, 10 Jun 1996 11:45:43 -0700 (PDT)
Cc: stable@freebsd.org
In-Reply-To: <199606101458.JAA20671@ulantris.infinop.com> from "John A. Booth" at "Jun 10, 96 09:58:51 am"
X-Mailer: ELM [version 2.4ME+ PL19 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-stable@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

John A. Booth writes:
> > What are the thoughts on breaking this stuff out of mail lists and into
> > news groups?  (At least there I can use kill files to eliminate the noise.)
> There are news groups or is a newsgroup.  My personal feeling is
> news takes too long to propagate.  I get much better response to the mailing
> lists--I'm more apt to read a mailing list than a news group.  If I don't
> think the subject applies I delete the messages w/o reading it.

I agree that there is way too much chatter here.  I used to follow the
other FreeBSD major mailing lists (-current, -question, and -hackers)
but for the same reasons, the avalanche of e-mail made it impossible
to hunt down those important announcements about tree changes, sup
servers, etc.  With the recent tree hosing on May 31, I was urged to
join this -stable mailing list so that I can stay informed of issues
that most affect maintaining a -stable system.  I hoped to do this
without having to dig through another 40 messages everyday to find the
gems.

Discussions about whether -stable should stay or go, or -current
should become what we think of as -stable, etc., or how commercial
users ought to donate money to FreeBSD, Inc., etc., are certainly
important.  But I think they should have their own place, like a
freebsd-planning (or -policy, or -harangue, or -etc) list.

--Morgan