The functionality is not experimental. It has been in our private stable branch for quite some time, and we had just not merged it into the tree. We've actually had quite a few requests from people to merge it into the next official release so they could update php via the FreeBSD ports system or whatnot without having to apply our patches, and compile by hand.
You should notice that very little had actually changed. It simply added a lot of Constants, and added one function "mcve_setssl_files".
I see no reason not to update the branch, especially since the changes are really non-intrusive.
I can back it out if necessary, as I don't want to adversely affect any policy you may have.
-Brad
Derick Rethans wrote:
On Tue, 8 Jul 2003, Brad House wrote:
bradmssw Mon Jul 7 23:16:38 2003 EDT
Modified files: (Branch: PHP_4_3)
/php-src/ext/mcve mcve.c php_mcve.h Log:
update mcve ext from HEAD. Sync with libmcve-3.2 functionality
Our policy is to put no new functionality in stable branches, can you explain why this is necessary?
regards, Derick
-- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
