On 9/11/05, Brooks Davis <[EMAIL PROTECTED]> wrote:
> > Either that, or we can deprecate PHP3/force upgrades to PHP4. But I'm
> > not sure if we'd want that. If it's mostly cruft, we can put this
> > kind of thing in now to allow upgrades (make sure the old handler
> > warns about PHP3) and then
On Sun, Sep 11, 2005 at 10:47:28AM -0400, michael chang wrote:
> On 9/11/05, Jeong Bae Kim <[EMAIL PROTECTED]> wrote:
> > Looks like a simple enough change to take the Apache basic authentication
> > password from PHP built-in global array, _SERVER.
>
> >From http://www.php.net/manual/en/features.
On 9/11/05, Martin Knoblauch <[EMAIL PROTECTED]> wrote:
> First of all, I am definitely in favour of doing 3.0.2 soon. Current
> CVS has the 64-bit disk accounting fix and the correct reporting of
> wio. both pretty critical bugs.
>
> As for what should go in my opinion is that we just should do
On 9/11/05, Jeong Bae Kim <[EMAIL PROTECTED]> wrote:
> Looks like a simple enough change to take the Apache basic authentication
> password from PHP built-in global array, _SERVER.
First of all, I am definitely in favour of doing 3.0.2 soon. Current
CVS has the 64-bit disk accounting fix and the correct reporting of
wio. both pretty critical bugs.
As for what should go in my opinion is that we just should do it and
increase the release frequency if more needed stuff comes
