From owner-freebsd-stable@FreeBSD.ORG Tue Oct 10 19:46:19 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E2BCE16A412 for ; Tue, 10 Oct 2006 19:46:19 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from server.baldwin.cx (66-23-211-162.clients.speedfactory.net [66.23.211.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id C9D5C43D70 for ; Tue, 10 Oct 2006 19:46:13 +0000 (GMT) (envelope-from jhb@freebsd.org) Received: from zion.baldwin.cx (zion.baldwin.cx [192.168.0.7]) (authenticated bits=0) by server.baldwin.cx (8.13.6/8.13.6) with ESMTP id k9AJjrIL089790; Tue, 10 Oct 2006 15:46:07 -0400 (EDT) (envelope-from jhb@freebsd.org) From: John Baldwin To: freebsd-stable@freebsd.org Date: Tue, 10 Oct 2006 15:45:49 -0400 User-Agent: KMail/1.9.1 References: <20061010173101.GA1160@panix.com> In-Reply-To: <20061010173101.GA1160@panix.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200610101545.49514.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (server.baldwin.cx [192.168.0.1]); Tue, 10 Oct 2006 15:46:08 -0400 (EDT) X-Virus-Scanned: ClamAV 0.88.3/2020/Tue Oct 10 14:11:22 2006 on server.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-4.4 required=4.2 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on server.baldwin.cx Cc: Joe Altman Subject: Re: I thought I had waited until a patch was issued for the SHA256 issue... 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: Tue, 10 Oct 2006 19:46:20 -0000 On Tuesday 10 October 2006 13:31, Joe Altman wrote: > to update world...I was it was recently committed, and ran an update > at approximately 10 AM EDT. > > Here is where 'make buildworld' stopped: The fix hasn't been committed yet. -- John Baldwin