Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:41946
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.198.233 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=j66MFsoMIiv/yZ5TKDtGxNvsdjHK6nBkZ/wvej9xVU9MQgppHfi1a9NyVvnMO2auw4
         JdLMS2JJq0rKPkmwmCFa7/3hX9dj6VbjlJPzhu2SyvezQQCg7ydf6kHKLZ/W2th3ZaEX
         bZmFtNsL0aPyYI7pTFi/dRW3WtJNdS8Cjr6GQ=
Message-ID: <fe05d1540811160527q4d6f92do981486fa1e2a3c3@mail.gmail.com>
Date: Sun, 16 Nov 2008 14:27:16 +0100
To: Mark <mark@hell.ne.jp>
Cc: internals@lists.php.net
In-Reply-To: <1226841788.14940.33.camel@localhost>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <cvs-account-2134@php.net>
	 <fe05d1540811160450y346eb802tbef31e39090b446f@mail.gmail.com>
	 <1226841788.14940.33.camel@localhost>
Subject: Re: [PHP-DEV] CVS Account Request: magicaltux
From: pierre.php@gmail.com ("Pierre Joye")

hi,

On Sun, Nov 16, 2008 at 2:23 PM, Mark <mark@hell.ne.jp> wrote:
> Hi,

> ... this one. You replied to my second reminder for bug #46127 to the
> internals mailing list with a promise to look at this patch later. This
> is the only reply I got from you for bug I posted on internals (as far
> as my mail client can tell).
>
> The patch is still not applied to CVS while it's a pretty simple one
> (just one added line to make accepted stream inherit context from their
> parent, which is exactly the same that can be found in stream ext).

Yes, it is not applied, but that does not change anything to my reply.
We are still in the same week (did not see this bug before)...


> With the release of PHP 5.2.7 closing by, I would love to see the WDDX
> bug (#46496) fixed in time, since it's making our, and other people's

I have nothing to do (not using it) with WDDX, it would be nice to
have an active maintainer for this extension but I can't decide on
what goes on or not, any other developers using it and can valid the
patches (and Mark's request to take the hand on it)?

Cheers,
-- 
Pierre

http://blog.thepimp.net | http://www.libgd.org