From owner-freebsd-stable Tue Jul 14 21:33:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA13121 for freebsd-stable-outgoing; Tue, 14 Jul 1998 21:33:45 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA13114 for ; Tue, 14 Jul 1998 21:33:42 -0700 (PDT) (envelope-from jfieber@indiana.edu) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.8.8/8.8.7) with SMTP id XAA06860; Tue, 14 Jul 1998 23:33:28 -0500 (EST) Date: Tue, 14 Jul 1998 23:33:28 -0500 (EST) From: John Fieber To: "J.D. Falk" cc: Subject: Re: New list? In-Reply-To: <19980714162128.34653@cybernothing.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 14 Jul 1998, J.D. Falk wrote: > Would it be possible to start a list specifically for known > problems with the current -STABLE code, perhaps announce-style > so that only FreeBSD developers with clue can post to it? Well, when people run out of interesting bugs to talk about, they get bored and start chattering about other things...like the amazing performance benefits of rack-mounting your computer. I think most of the easy to fix things in -stable either have been fixed or are pretty non-essential. Some of the bigger problems, like NFS, are being attacked in 3.0 and the effort of bringing it back to 2.x is deemed too large considering the volunteer resources available. Basically, life in -stable land is blissfully dull at the moment. :) -john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message