From owner-freebsd-ports@FreeBSD.ORG Sun Aug 10 09:42:10 2003 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 024EC37B401; Sun, 10 Aug 2003 09:42:09 -0700 (PDT) Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6EE8443F93; Sun, 10 Aug 2003 09:42:09 -0700 (PDT) (envelope-from linimon@lonesome.com) Received: by mail.soaustin.net (Postfix, from userid 502) id E88E1142DC; Sun, 10 Aug 2003 11:42:08 -0500 (CDT) Date: Sun, 10 Aug 2003 11:42:08 -0500 (CDT) From: Mark Linimon X-X-Sender: linimon@pancho To: Kris Kennaway In-Reply-To: <20030810062254.GA11719@rot13.obsecurity.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: Greg 'groggy' Lehey cc: ports@FreeBSD.org Subject: Re: Ports scheduled for removal on Nov 7 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Aug 2003 16:42:10 -0000 > I think it would definitely be off-topic for freebsd-questions, but > I'd be more open to -announce. The only thing is that port removals > are a periodic event (I just happen to have more than usual queued up > this time), so if I do it this time I should do it every time. Well, I can suggest a class of messages such as (ports scheduled for deletion|changes to ports framework that will affect various ports|freeze in effect|freeze lifted), possibly others. I think there would be an audience for this mailing list who would not otherwise be able to follow the large-volume ports mailing lists. freebsd-ports-announce? mcl