Date: Fri, 11 May 2007 10:25:54 +0200 From: Alexander Leidinger <Alexander@Leidinger.net> To: Kris Kennaway <kris@obsecurity.org> Cc: ports@freebsd.org Subject: Re: php 5.2.2 Message-ID: <20070511102554.yafdk0vhck4c4woo@webmail.leidinger.net> In-Reply-To: <20070510085546.GA79380@xor.obsecurity.org> References: <200705100048.l4A0mULd078168@app.auscert.org.au> <20070510012520.GC18342@soaustin.net> <5fbf03c20705100125t57435f94ycaf472ad0c6303d7@mail.gmail.com> <20070510085546.GA79380@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Quoting Kris Kennaway <kris@obsecurity.org> (from Thu, 10 May 2007 =20 04:55:46 -0400): > On Thu, May 10, 2007 at 10:25:56AM +0200, Spil Oss wrote: >> As much as I (and I hope all of us) appreciate the effort to include >> xorg7.2, this leaves many productive systems vulnerable. I have not >> yet found an update on the progress of the xorg7.2 work but I'm >> anxious to find out when we can expect the ports tree to be unfrozen. >> >> Can anyone supply us with a timeline for php 5.2.2? > > http://www.freebsd.org/cgi/query-pr.cgi?pr=3Dports/112527 > > Just apply it, relax, and stop bugging us. Thanks :) This leads me to the question if it is like a normal ports freeze: Can =20 we (committers) submit patches (important ones like security/failure =20 fixes) to portmgr and ask for commit approval, or is this some kind of =20 very hard lockdown of the tree? Bye, Alexander. --=20 =09"Your son still sliding down the banisters?" =09"We wound barbed wire around them." =09"That stop him?" =09"No, but it sure slowed him up." http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID =3D B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID =3D 72077137
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070511102554.yafdk0vhck4c4woo>