Fwd: [Ming-dev] PHP Integration

[Dave H. <da...@op...>]

Whoops.  Forgot to reply to the list..

Begin forwarded message:

> From: Dave Hayden <da...@op...>
> Date: Thu Aug 08, 2002  12:31:00 PM US/Pacific
> To: "Steve Alberty" <al...@ne...>
> Subject: Re: [Ming-dev] PHP Integration
>
>
> On Thursday, August 8, 2002, at 04:00 AM, Steve Alberty wrote:
>
>> i've seen that Dave has back porting ming.c from PHP 4.2.2.
>>
>> It is principal a good idea, but Dave has overwritten my change in this
>> file, and I have also back porting ming.c from 4.3.0dev.
>
> Crap.  Sorry.  I don't keep up with the PHP API changes, so I just saw 
> that the CVS ming.c didn't work and the php-4.2.2 ming.c did, so I 
> assumed we were out of date.  I added the PHP-4.3.0dev ming.c in as 
> ming-dev.c.  I'm guessing most people who pull Ming from CVS won't be 
> using the dev version of PHP..
>
>> We should more coordinate the back porting from php tree.
>>
>> I can commit every changes in php_ext/* the php cvs tree, because I 
>> have
>> PHP CVS access. I think we should stop the back porting and make all 
>> the
>> changes in the ming tree.
>
> It's always nice when PHP is up to date with Ming.  Do you have any 
> idea when 4.3 is due out?  I aim to have an Official Release of Ming 
> out the door in the next week, so if that's before the next PHP release 
> we should definitely get a current ming.c into the new PHP.
>
> As I said, though, I don't keep up with the PHP changes, so I don't 
> know what will work best for those who do..
>
> -D
>