From owner-cvs-ports@FreeBSD.ORG Wed Feb 7 21:07:15 2007 Return-Path: X-Original-To: cvs-ports@FreeBSD.org Delivered-To: cvs-ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CB04716A401; Wed, 7 Feb 2007 21:07:15 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id A01DA13C48D; Wed, 7 Feb 2007 21:07:15 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id 1E730589; Wed, 7 Feb 2007 15:07:15 -0600 (CST) Date: Wed, 7 Feb 2007 15:07:15 -0600 To: Kris Kennaway Message-ID: <20070207210715.GB29854@soaustin.net> References: <200702071452.l17Eqvll083171@repoman.freebsd.org> <20070207150415.GQ16049@droso.net> <20070207152452.GA57244@heechee.tobez.org> <20070207210003.GA88968@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070207210003.GA88968@xor.obsecurity.org> User-Agent: Mutt/1.5.9i From: linimon@lonesome.com (Mark Linimon) Cc: cvs-ports@FreeBSD.org, cvs-all@FreeBSD.org, Anton Berezin , ports-committers@FreeBSD.org Subject: Re: cvs commit: ports/math/p5-Math-BigInt Makefile distinfo X-BeenThere: cvs-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Feb 2007 21:07:15 -0000 On Wed, Feb 07, 2007 at 04:00:04PM -0500, Kris Kennaway wrote: > In a week or two we'll be committing a cleanup patch that removes all > support for unsupported versions of FreeBSD from bsd.port.mk and > related files. 4.x is now dead and soon to be entirely buried as far > as ports are concerned, so you might as well finish the deed in your > ports. I'll reiterate that we've been saying this for over a year now. Those who aren't able to migrate to 6.2 need to ping me with my bugmeister hat on so I can try to prioritize any PRs about that. I also intend to get a task-force started going through the PR backlog for everything prior to 5.5/6.1 and find out whether they still apply, and, if not, close them. >From what I can tell, 6.2 has a very small number of bug reports against it relative to prior releases, and many performance improvements are now being testing in -CURRENT, so I'd like to see everyone who does not have some kind of special need move towards 6.2. It's long past time we moved forward. mcl