From owner-freebsd-hackers@FreeBSD.ORG Sun Oct 5 11:21:46 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9CC9916A4B3 for ; Sun, 5 Oct 2003 11:21:46 -0700 (PDT) Received: from smtp.omnis.com (smtp.omnis.com [216.239.128.26]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0363043FAF for ; Sun, 5 Oct 2003 11:21:46 -0700 (PDT) (envelope-from wes@softweyr.com) Received: from foogate.softweyr.com (66-91-236-204.san.rr.com [66.91.236.204]) by smtp-relay.omnis.com (Postfix) with ESMTP id B26D75B652; Sun, 5 Oct 2003 11:20:19 -0700 (PDT) From: Wes Peters Organization: Softweyr LLC To: "Dan Langille" , Daniel Eischen Date: Sun, 5 Oct 2003 11:21:29 -0700 User-Agent: KMail/1.5.2 References: <3F77D27E.6203.3321BA14@localhost> <3F7E9F1D.14593.4DB108E2@localhost> In-Reply-To: <3F7E9F1D.14593.4DB108E2@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200310051121.29282.wes@softweyr.com> cc: hackers@freebsd.org Subject: Re: [PATCH] : libc_r/uthread/uthread_write.c X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Oct 2003 18:21:46 -0000 On Saturday 04 October 2003 07:21 am, Dan Langille wrote: > On 4 Oct 2003 at 10:17, Daniel Eischen wrote: > > On Mon, 29 Sep 2003, Dan Langille wrote: > > > All our testing on this patch has been successful. I'm going to > > > do a few more tests on different hardware under 4.8-stable. > > > > > > What's the next step? Commit it? Get others to test with it > > > first? > > > > It's already in -current. > > Thanks for that commit. > > > You'll have to wait for the code > > freeze to thaw in -stable before it goes in there. > > Bugger... which means it won't be into 4.9-RELEASE. If it is important, forward the code and the reason it is needed to re@. Code freeze means 'only critical bug fixes'; if this is one of those, let's get it in. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/