From owner-freebsd-current@FreeBSD.ORG Wed Sep 10 16:41:10 2003 Return-Path: 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 8515116A4BF for ; Wed, 10 Sep 2003 16:41:10 -0700 (PDT) Received: from meitner.wh.uni-dortmund.de (meitner.wh.Uni-Dortmund.DE [129.217.129.133]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9912343FFB for ; Wed, 10 Sep 2003 16:41:09 -0700 (PDT) (envelope-from michaelnottebrock@gmx.net) Received: from lofi.dyndns.org (pc2-105.intern.meitner [10.3.12.105]) by meitner.wh.uni-dortmund.de (Postfix) with ESMTP id B740D167615; Thu, 11 Sep 2003 01:41:08 +0200 (CEST) Received: from gmx.net (kiste.my.domain [192.168.8.4]) (authenticated bits=0) by lofi.dyndns.org (8.12.9/8.12.9) with ESMTP id h8ANf726078655 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 11 Sep 2003 01:41:08 +0200 (CEST) (envelope-from michaelnottebrock@gmx.net) Message-ID: <3F5FB691.3040403@gmx.net> Date: Thu, 11 Sep 2003 01:41:05 +0200 From: Michael Nottebrock User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax) X-Accept-Language: en-us, en, de-de MIME-Version: 1.0 To: Steve Kargl References: <3F5F2774.9010408@gmx.net> <20030910144620.GA2438@troutmask.apl.washington.edu> <3F5F420B.5030202@gmx.net> <20030910165645.GA2839@troutmask.apl.washington.edu> In-Reply-To: <20030910165645.GA2839@troutmask.apl.washington.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new cc: freebsd-current@FreeBSD.org Subject: Re: Quo vadis, -CURRENT? (recent changes to cc & compatibility) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Wed, 10 Sep 2003 23:41:10 -0000 Steve Kargl wrote: > Why? The portmgr can tag the ports collection at any point in > time before or after the -pthread deprecation date. Steve, ports-freeze dates are set and published ahead of time just as dates for releases are. It's obviously not a good thing to have to try and be very conservative with commits to ports (in order to have a maximum number of them working for the next 4.x release) while at the same time there is loud demand for fixing a big number of them for -CURRENT. Don't bother telling me I'm whining, pointing at the handbook again and saying "don't expect anything to work on -CURRENT at any given time", you're shooting the messenger. -- ,_, | Michael Nottebrock | lofi@freebsd.org (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org