From owner-freebsd-current@FreeBSD.ORG Fri Aug 9 21:32:03 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 61150F3B; Fri, 9 Aug 2013 21:32:03 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 3A779244B; Fri, 9 Aug 2013 21:32:03 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id B75A1B939; Fri, 9 Aug 2013 17:31:59 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org Subject: Re: HEAD in dubious state after 254141, update to 254163+ Date: Fri, 9 Aug 2013 17:16:05 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p28; KDE/4.5.5; amd64; ; ) References: <201308091603.33445.jhb@freebsd.org> In-Reply-To: <201308091603.33445.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201308091716.05948.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Fri, 09 Aug 2013 17:31:59 -0400 (EDT) Cc: current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Aug 2013 21:32:03 -0000 On Friday, August 09, 2013 4:03:33 pm John Baldwin wrote: > I'm in the process of reverting 254150 and 254141. I think the changes in > 254141 were from an old tree that wasn't updated for the changes in 254138 and > I don't seen an obvious way to fix 254141, so until Attilio can redo 254141 > I'm going to revert these. Alan submitted a fix for the 254141 and I've booted it successfully so I've commited that. However, please be sure to update to at least 254163. -- John Baldwin