From owner-freebsd-stable@FreeBSD.ORG Tue Mar 6 06:59:48 2012 Return-Path: Delivered-To: stable@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [69.147.83.53]) by hub.freebsd.org (Postfix) with ESMTP id DC361106564A; Tue, 6 Mar 2012 06:59:48 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from [127.0.0.1] (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 2B25914FA17; Tue, 6 Mar 2012 06:59:48 +0000 (UTC) Message-ID: <4F55B5E3.1080207@FreeBSD.org> Date: Tue, 06 Mar 2012 00:59:47 -0600 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: Adrian Chadd References: <20120221143537.Horde.deyFDZjmRSRPQ52pxBIpnLA@webmail.leidinger.net> <4F4BA707.5070608@wasikowski.net> <4F4C3FE7.3040802@FreeBSD.org> <4F4D51CB.2010508@FreeBSD.org> <4F4D5E5D.9040302@FreeBSD.org> <4F4DD288.5060106@FreeBSD.org> <4F4ED889.2070608@FreeBSD.org> <4F500BB9.4040307@FreeBSD.org> <4F5088CA.1090108@FreeBSD.org> <4F510FBD.50008@FreeBSD.org> <4F5117A6.2030003@FreeBSD.org> <4F5285CF.3010001@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.3.5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org, current@freebsd.org, =?UTF-8?B?eiBXxIVzaWtvd3NraQ==?= , Arnaud Lacombe , "Bjoern A. Zeeb" , Alexander Leidinger Subject: Re: flowtable usable or not 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, 06 Mar 2012 06:59:49 -0000 On 3/4/2012 2:04 PM, Adrian Chadd wrote: > 2012/3/3 Doug Barton : >> On 03/02/2012 16:05, Adrian Chadd wrote: >>> Try breaking that cycle. >> >> ... one of the things I've been asking for years. :) >> >> Julian's right though, I think PC-BSD will help, but I still think that >> committers should run -current. I've asked privately for our committers >> to go back to -current and then have some dedicated development time >> where we work together to fix the problems that *we* find in order to >> make the project more desktop-friendly overall. I was (figuratively) >> laughed out of the room. > > There's a magic intersection between "need to run current" and "need > to keep stuff unbroken enough to get work done." Personally I have a -current partition (slice) that I keep up to date, and an 8-stable'ish slice that I purposely keep in a known-good state, and only update if -current has been running good for a while (which it has more often than not in the last several years). I have both slices set up to share data such as /home, my cvs and svn trees, etc. This has worked really well for me (and others, I originally got the idea and some of my configuration from David Wolfskill) for over a decade. hth, Doug