Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:2678 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 93367 invoked from network); 24 Jun 2003 04:25:03 -0000 Received: from unknown (HELO mail.zend.com) (192.117.235.230) by pb1.pair.com with SMTP; 24 Jun 2003 04:25:03 -0000 Received: (qmail 11096 invoked from network); 24 Jun 2003 04:24:50 -0000 Received: from localhost (HELO andi-home.zend.com) (127.0.0.1) by localhost with SMTP; 24 Jun 2003 04:24:50 -0000 Message-ID: <5.1.0.14.2.20030624072449.0da0cea8@127.0.0.1> X-Sender: andi@127.0.0.1 X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Tue, 24 Jun 2003 07:28:40 +0200 To: Sascha Schumann ,internals@lists.php.net In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: Re: [PHP-DEV] Automated selection of engine From: andi@zend.com (Andi Gutmans) References: At 05:25 AM 6/24/2003 +0200, Sascha Schumann wrote: > So, we should get comfortable with the idea of having a Zend > _and_ a ZendEngine2 dir at the same time(*). > > Thoughts? I think in the long run it tends to be a bit ugly, but I don't see any alternative right now, because merging the CVS histories doesn't seem to be feasible to me. So I'm OK with it for now. However, I am not convinced that having to explicitly checkout the PHP_5 branch is such a good idea. I thought the idea was to have HEAD be the current development version and branch if off when necessary. I would prefer this kind of approach. Andi