From owner-freebsd-current Sun Aug 20 22:25:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from magnesium.net (toxic.magnesium.net [207.154.84.15]) by hub.freebsd.org (Postfix) with SMTP id D676A37B424 for ; Sun, 20 Aug 2000 22:25:18 -0700 (PDT) Received: (qmail 99194 invoked by uid 1142); 21 Aug 2000 05:25:13 -0000 Date: 20 Aug 2000 22:25:13 -0700 Date: Sun, 20 Aug 2000 22:22:44 -0700 From: Jason Evans To: Nik Clayton Cc: current@freebsd.org Subject: Re: HEADS UP: Destabilization due to SMP development Message-ID: <20000820222244.O14875@blitz.canonware.com> References: <20000619115330.D79318@blitz.canonware.com> <20000820121405.A2298@kilt.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000820121405.A2298@kilt.nothing-going-on.org>; from nik@freebsd.org on Sun, Aug 20, 2000 at 12:14:05PM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Aug 20, 2000 at 12:14:05PM +0000, Nik Clayton wrote: > On Mon, Jun 19, 2000 at 11:53:30AM -0700, Jason Evans wrote: > > Summary: -current will be destabilized for an extended period (on the order > > of months). A tag (not a branch) will be laid down before the initial > > checkin, and non-developers should either stick closely to that tag until > > the kernel stabilizes, or expect large doses of pain. This tag will be > > laid down as soon as June 26, 00:00 PST, with a minimum 24 hour warning > > beforehand. > > Is there any news on this work? Unless I've missed the significance of > recent commits, I haven't seen anything approaching this sort of > destabilisation in -current. No, there has not been a commit yet, but we're quite close at this point to making one. Chances are good that this will happen within the next two weeks. Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message