From owner-freebsd-current Sun Apr 18 10:13:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id A1E6D14DC1 for ; Sun, 18 Apr 1999 10:13:34 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id KAA00600; Sun, 18 Apr 1999 10:11:08 -0700 (PDT) (envelope-from jkh@zippy.cdrom.com) To: Alex Zepeda Cc: current Subject: Re: newbus and modem(s) In-reply-to: Your message of "Sun, 18 Apr 1999 09:13:46 PDT." Date: Sun, 18 Apr 1999 10:11:08 -0700 Message-ID: <598.924455468@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Which means that it perhaps should be worked out before being merged. Take > for instance CAM. It didn't work perfectly, but it sure got a lot more > exposure than newbus, and when it was integrated it caused very few > problems. The two systems aren't equivalent so it's not really correct to make comparisons like this. In any case, -current has always been designated for developers to work on issues precisely like this one and it's simply not accurate to suggest that bleeding edge development should not be done in the -current branch. As I said before, it only points out that many people are tracking the wrong branch. If you want a smooth experience, track -stable and that's all I'm going to say on the issue. > Well, why not make ext2fs the default fs just to shake things up? It's If there were a truly practical reason to do so, you may rest assured that we would. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message