From owner-freebsd-current@FreeBSD.ORG Sat Mar 11 01:55:46 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6E2AE16A420 for ; Sat, 11 Mar 2006 01:55:45 +0000 (GMT) (envelope-from b.candler@pobox.com) Received: from proof.pobox.com (proof.pobox.com [207.106.133.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 283904672A for ; Fri, 10 Mar 2006 15:43:14 +0000 (GMT) (envelope-from b.candler@pobox.com) Received: from proof (localhost [127.0.0.1]) by proof.pobox.com (Postfix) with ESMTP id 504D998264; Fri, 10 Mar 2006 10:43:08 -0500 (EST) Received: from mappit.local.linnet.org (212-74-113-67.static.dsl.as9105.com [212.74.113.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by proof.sasl.smtp.pobox.com (Postfix) with ESMTP id 1C42121F79; Fri, 10 Mar 2006 10:43:07 -0500 (EST) Received: from lists by mappit.local.linnet.org with local (Exim 4.60 (FreeBSD)) (envelope-from ) id 1FHjlh-0007iK-Qj; Fri, 10 Mar 2006 15:43:05 +0000 Date: Fri, 10 Mar 2006 15:43:05 +0000 From: Brian Candler To: Alain Hebert Message-ID: <20060310154305.GA29639@uk.tiscali.com> References: <4410F0BE.6050600@pubnix.net> <200603100604.48535.thierry@herbelot.com> <441112DB.9060907@pubnix.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <441112DB.9060907@pubnix.net> User-Agent: Mutt/1.4.2.1i Cc: freebsd-current@freebsd.org Subject: Re: HowTo?: Current -> RELENG_6_0 Patch for "semaphore timeout !! DANGER Will Robinson !!" issue with Promise Fasttrak Raid 0/1 Card X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Sat, 11 Mar 2006 01:55:46 -0000 On Fri, Mar 10, 2006 at 12:47:07AM -0500, Alain Hebert wrote: > I looked/search everywhere for a thread. I just used the wrong > keywords it seems. > > I'll try -current tomorrow... I hope its stable enought for production. What you want is RELENG_6 (aka 6-STABLE). That gets you tracking the code base which will end up shortly as 6.1-RELEASE, not the bleeding edge -CURRENT. You can then continue tracking RELENG_6 and you'll incrementally get all the changes which will end up in 6.2, 6.3 etc. Regards, Brian.