From owner-freebsd-smp Tue Jun 20 12:42:40 2000 Delivered-To: freebsd-smp@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id B2BC437B7C4 for ; Tue, 20 Jun 2000 12:42:36 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id MAA17797; Tue, 20 Jun 2000 12:42:01 -0700 Date: Tue, 20 Jun 2000 12:41:36 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Warner Losh Cc: Poul-Henning Kamp , Matthew Dillon , freebsd-smp@FreeBSD.ORG Subject: Re: SMP discussion moving to freebsd-smp In-Reply-To: <200006201936.NAA71564@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I don't think I entirely agree that "-current must always be buildable and runnable" in that I believe we all *did* understand that there would be breakage for the BSD/OS merge- at least I did. I also would have suggested a branch myself (despite the pain to those working on the branch), or the adoption of a better merge/toolset technology (like bitkeeper, for example). The problem here is that we cannot plan for such breakage, either to assist or get out of the way, when all we get are edicts that "this is happening" with no clue as to what the architectural or procedural choices are. But, frankly, the matter now all speaks for itself. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message