From owner-freebsd-stable Fri Jun 8 7:51:53 2001 Delivered-To: freebsd-stable@freebsd.org Received: from winston.osd.bsdi.com (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id 73C5C37B405 for ; Fri, 8 Jun 2001 07:51:43 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.3/8.11.3) with ESMTP id f58EpEO03285; Fri, 8 Jun 2001 07:51:14 -0700 (PDT) (envelope-from jkh@osd.bsdi.com) To: kmays2000@hotmail.com Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Improvements for FreeBSD v4.3.1-Release? In-Reply-To: References: X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20010608075114N.jkh@osd.bsdi.com> Date: Fri, 08 Jun 2001 07:51:14 -0700 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 31 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG From: "Kenneth Mays" Subject: Improvements for FreeBSD v4.3.1-Release? Date: Fri, 08 Jun 2001 10:35:17 -0400 > So far: > > 1. Fix tar issues If there's a list of PRs to accompany this request, it will be far more likely to be addressed. Saying "fix tar issues" is far too vague to work with, even for volunteer engineers. :) > 2. Journalling FS (what's the best one out there?) This is never going to happen for 4.4 no matter what. A change of that magnitude would go into 5.0 first and unleashing experimental filesystem code on people is not what the -stable branch is all about. > 3. Robust USB 2.0 and peripheral drivers See above comment about citing PRs. Using "robust" in this context is tantamount to saying: "TODO: Make kernel better. Lots better." That might make a good bullet point in some general mission statement, but as a TODO list item it's again far too vague to be of much use. If there are areas where the USB code is lacking specific support for a given piece of hardware then that hardware should be enumerated in a PR somewhere. If it falls over when you plug a foo device in, that should also be a PR. Those are the kinds of thing that some engineer can come along and pick up as a project. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message