From owner-freebsd-stable@FreeBSD.ORG Thu Aug 28 02:27:08 2008 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3B27D1065682; Thu, 28 Aug 2008 02:27:08 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id D06148FC1D; Thu, 28 Aug 2008 02:27:07 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (zion.baldwin.cx [IPv6:2001:470:1f11:75:2a0:d2ff:fe18:8b38]) (authenticated bits=0) by server.baldwin.cx (8.14.2/8.14.2) with ESMTP id m7S2QOP2075084; Wed, 27 Aug 2008 22:27:01 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-stable@freebsd.org Date: Wed, 27 Aug 2008 22:25:37 -0400 User-Agent: KMail/1.9.7 References: In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Message-Id: <200808272225.38151.jhb@freebsd.org> Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [IPv6:2001:470:1f11:75::1]); Wed, 27 Aug 2008 22:27:01 -0400 (EDT) X-Virus-Scanned: ClamAV 0.93.1/8103/Wed Aug 27 20:41:49 2008 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.5 required=4.2 tests=AWL,BAYES_00,NO_RELAYS autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: Robert Watson Subject: Re: WARNING: 7-STABLE BROKEN -- please wait to upgrade / Should be OK now X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Aug 2008 02:27:08 -0000 On Wednesday 27 August 2008 01:29:43 pm Robert Watson wrote: > On Wed, 27 Aug 2008, Robert Watson wrote: > > It looks like there have been several mismerges in the DTrace MFC. We're > > currently assessing the damage to decide if it should be entirely backed > > out, or if we can just do some selective patching up. In the mean time, > > please don't try to update -- wait for an all clear. > > Just an update: John Baldwin has identified the set of problematic parts to > the change, and will shortly be backing them out. Please continue to wait > on updating to the latest 7-STABLE until an explicit all clear message is > sent. I believe things should be fine on 7-stable now. -- John Baldwin