Re: Re: cvs: php-src /ext/mysql php_mysql.c /ext/mysqli mysqli.c /ext/mysqlnd mysqlnd.c mysqlnd_palloc.c mysqlnd_ps.c mysqlnd_wireprotocol.c
| From: | Pierre Joye | Date: | Tue, 15 Jul 2008 16:11:20 +0000 |
| Subject: | Re: Re: cvs: php-src /ext/mysql php_mysql.c /ext/mysqli mysqli.c /ext/mysqlnd mysqlnd.c mysqlnd_palloc.c mysqlnd_ps.c mysqlnd_wireprotocol.c | ||
| References: | 1 2 3 4 5 6 7 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-38969@lists.php.net to get a copy of this message | ||
On Tue, Jul 15, 2008 at 5:42 PM, Ulf Wendel <ulf.wendel@phpdoc.de> wrote:
> What's your point, what requests are you talking about?
Please ask Johannes, I told them to him live last time we met. If
there is doubts, I will happily repeat them.
> I saw one person complaining about mysqlnd being compiled into PHP although
> no mysql extension was compiled into PHP: bug - open to anybody to fix.
Ok, I will fix that as It does not make sense to enable mysqlnd when
no mysql extensions are enabled (but that's the least of my worries).
> PHP has a
> very vivid team of developers fixing many issues before they go down to the
> maintainers, see the constant work on bug reports. I relied on that to
> happen. Is that the issue you are talking about?
How can that happen when you do many maybe unrelated changes in one
commit? How can I (or other) granulary review a commit in this case
(if something is broken)?
We are one week before a freeze and we just see than one of the most
important change for this release is developed outside our tree, I
seriously hope that you understand our worries (I'm not alone to
worry). We may not have have the time to deal with the last minutes
issues introduced by a last minute sync (== disable).
--
Pierre
http://blog.thepimp.net | http://www.libgd.org