From owner-freebsd-gnome@FreeBSD.ORG Wed Jun 16 22:09:21 2004 Return-Path: Delivered-To: freebsd-gnome@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8191316A4CE for ; Wed, 16 Jun 2004 22:09:21 +0000 (GMT) Received: from smtp01.mrf.mail.rcn.net (smtp01.mrf.mail.rcn.net [207.172.4.60]) by mx1.FreeBSD.org (Postfix) with ESMTP id 53F8843D1F for ; Wed, 16 Jun 2004 22:09:21 +0000 (GMT) (envelope-from adam.mclaurin@gmx.net) Received: from 209-150-62-14.c3-0.arl-ubr1.sbo-arl.ma.cable.rcn.com ([209.150.62.14] helo=jake) by smtp01.mrf.mail.rcn.net with smtp (Exim 3.35 #7) id 1BaiZc-00023z-00 for gnome@freebsd.org; Wed, 16 Jun 2004 18:08:00 -0400 Date: Wed, 16 Jun 2004 18:07:59 -0400 From: Adam McLaurin To: gnome@freebsd.org Message-Id: <20040616180759.23876558.adam.mclaurin@gmx.net> In-Reply-To: <1087420025.21533.39.camel@zircon> References: <1087418469.21533.27.camel@zircon> <1087419008.888.28.camel@gyros> <1087420025.21533.39.camel@zircon> X-Mailer: Sylpheed version 0.9.11-gtk2-20040613 (GTK+ 2.4.3; i386-portbld-freebsd5.2.1) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: firefox 0.9 does not work X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jun 2004 22:09:21 -0000 On Wed, 16 Jun 2004 14:07:06 -0700 Joe Kelsey wrote: > What are you talking about? I run 4-STABLE, no message in UPDATING! http://www.freebsd.org/cgi/cvsweb.cgi/ports/UPDATING?rev=1.30&content-type=text/x-cvsweb-markup That was committed almost 22 hours ago, and clearly states the new Firefox requirement. > I do not find any reason that I need to monitor ports@ or to read CVS > commit messages, unless you have chosen to create a brand-new > requirement out of whole cloth that says that I need to monitor ports@ > all of a sudden. > > If you make a change like this in a standard gnome application, you > need to at least mention it on the gnome@ list or somehow make it a > requirement that everyone who monitors gnome@ no has to *also* monitor > ports@. Yet another moron that slaps the hand that feeds him ... This is the exact reason why UPDATING was created (3 months ago!), and the exact reason you should read it EVERY time you cvsup BEFORE you start upgrading ANYTHING. I have even put it in my cvsup script, so I'll never forget to read it. -- Adam "satyam, shivam, sundaram"