Date: Wed, 16 Jun 2004 18:07:59 -0400 From: Adam McLaurin <adam.mclaurin@gmx.net> To: gnome@freebsd.org Subject: Re: firefox 0.9 does not work 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>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 16 Jun 2004 14:07:06 -0700 Joe Kelsey <joe@zircon.seattle.wa.us> 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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040616180759.23876558.adam.mclaurin>