From owner-freebsd-ports Mon Apr 26 17:21:34 1999 Delivered-To: freebsd-ports@freebsd.org Received: from cerberus.student.umd.edu (cerberus.student.umd.edu [129.2.178.155]) by hub.freebsd.org (Postfix) with ESMTP id 9212014CD0; Mon, 26 Apr 1999 17:21:28 -0700 (PDT) (envelope-from bfoz@glue.umd.edu) Received: from glue.umd.edu (poseidon.student.umd.edu [129.2.179.31]) by cerberus.student.umd.edu (8.9.2/8.9.2) with ESMTP id UAA92280; Mon, 26 Apr 1999 20:21:27 -0400 (EDT) (envelope-from bfoz@glue.umd.edu) Message-ID: <3725028E.AE924BE8@glue.umd.edu> Date: Mon, 26 Apr 1999 20:19:26 -0400 From: Brandon Fosdick X-Mailer: Mozilla 4.51 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "Jonathan M. Bresler" Cc: wosch@panke.de.freebsd.org, ports@FreeBSD.ORG, asami@FreeBSD.ORG Subject: Re: Mailing list freebsd-port-announce References: <19990427001535.3677014DF3@hub.freebsd.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Jonathan M. Bresler" wrote: > > > Many users ask me if I can sent the 'New ports added/updated last two > > weeks' mail to a low volume mailing list. > > > > freebsd-announce is not the right mailing list - some users > > don't wants ports information or large mails. > > > > So I think we should setup a moderated freebsd-port-announce > > mailing list. > > you may be right......or perhpas we can create a > ports-announce web page which will contain each 'new ports' message > as it is generated. not too much to ask for them to check one web > page every two weeks. > > thoughts? Would it be feasible to dump the 'new ports' messages into a database and have the web page created dynamically? More initial setup, but less maintenance. -Brandon -- bfoz@starfleet.umd.edu "In life there are those who steer, and those who push" "I'm not impatient, the world is too slow" "Life is short, so have fun, play hard, and leave a good looking corpse" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message