From owner-freebsd-current Sat Sep 16 15:27:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 9E57C37B42C for ; Sat, 16 Sep 2000 15:27:40 -0700 (PDT) Received: (from jhb@localhost) by pike.osd.bsdi.com (8.9.3/8.9.3) id PAA26908; Sat, 16 Sep 2000 15:27:02 -0700 (PDT) (envelope-from jhb) From: John Baldwin Message-Id: <200009162227.PAA26908@pike.osd.bsdi.com> Subject: Re: Questions about PRE_SMPNG (Was PRE_SMPNG snap) In-Reply-To: from James Johnson at "Sep 16, 2000 01:16:04 pm" To: James Johnson Date: Sat, 16 Sep 2000 15:27:02 -0700 (PDT) Cc: "Brandon D. Valentine" , current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL68 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG James Johnson wrote: > Can someone explain why we have a PRE_SMPNG tag? Sure there may be some > issues with SMP in -CURRENT right now, however simply avoiding running the > code is not going to get those issues fixed. It calms peoples fears, and because people asked for it. Generally, trying to allay fears about major changes that have potential for great breakage is much more work than one extra cvs command to lay down a tag. :) -- John Baldwin -- http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message