Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:74498 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 17959 invoked from network); 26 May 2014 10:53:03 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 26 May 2014 10:53:03 -0000 Authentication-Results: pb1.pair.com header.from=ajf@ajf.me; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=ajf@ajf.me; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain ajf.me designates 192.64.117.65 as permitted sender) X-PHP-List-Original-Sender: ajf@ajf.me X-Host-Fingerprint: 192.64.117.65 erelay5.ox.registrar-servers.com Received: from [192.64.117.65] ([192.64.117.65:42158] helo=erelay5.ox.registrar-servers.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 45/D9-60353-D0D13835 for ; Mon, 26 May 2014 06:53:02 -0400 Received: from localhost (unknown [127.0.0.1]) by erelay1.ox.registrar-servers.com (Postfix) with ESMTP id 312FE22049D1; Mon, 26 May 2014 10:52:59 +0000 (UTC) Received: from erelay1.ox.registrar-servers.com ([127.0.0.1]) by localhost (erelay.ox.registrar-servers.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id HrocPrqQc7f4; Mon, 26 May 2014 06:52:58 -0400 (EDT) Received: from imap4-1.ox.privateemail.com (imap4-1.ox.privateemail.com [198.187.29.243]) by erelay1.ox.registrar-servers.com (Postfix) with ESMTP id 2B41522049C8; Mon, 26 May 2014 06:52:58 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by mail.privateemail.com (Postfix) with ESMTP id D9AD8560071; Mon, 26 May 2014 06:52:57 -0400 (EDT) X-Virus-Scanned: Debian amavisd-new at imap4.ox.privateemail.com Received: from mail.privateemail.com ([127.0.0.1]) by localhost (imap4.ox.privateemail.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 1V5E6tVnx0rl; Mon, 26 May 2014 06:52:57 -0400 (EDT) Received: from [192.168.0.200] (unknown [90.203.28.11]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.privateemail.com (Postfix) with ESMTPSA id 4C796560079; Mon, 26 May 2014 06:52:55 -0400 (EDT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\)) In-Reply-To: Date: Mon, 26 May 2014 11:52:51 +0100 Cc: PHP Internals Content-Transfer-Encoding: quoted-printable Message-ID: <44A0430A-9E30-43B7-855F-23ACC5FE0E81@ajf.me> References: To: Julien Pauli X-Mailer: Apple Mail (2.1878.2) Subject: Re: [PHP-DEV] Documenting APIs and merging ideas From: ajf@ajf.me (Andrea Faulds) On 26 May 2014, at 11:37, Julien Pauli wrote: > If some start hacking based on master, they'll hit problems the time > phpng gets merged (if it is to be merged). And the same applies > reversed : how can phpng contributors integrate in their branch ideas > from other developers and branches ? > Wasn't it the case for the int64 patch from Pierre ? This problem has been bothering me as well. There=92s stuff I=92d like = to =97 or at least attempt to ;) =97 do in Zend, but phpng isn=92t = merged yet so I fear having to redo much of it once it=92s merged. I suggest we only work on stuff which won=92t touch Zend, or at least = won=92t touch stuff phpng touches, until phpng is merged. However, this = is assuming phpng won=92t take too long. -- Andrea Faulds http://ajf.me/