Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:39885 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 85711 invoked from network); 12 Aug 2008 15:45:44 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 12 Aug 2008 15:45:44 -0000 Authentication-Results: pb1.pair.com smtp.mail=tony@daylessday.org; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=tony@daylessday.org; sender-id=pass Received-SPF: pass (pb1.pair.com: domain daylessday.org designates 89.208.40.236 as permitted sender) X-PHP-List-Original-Sender: tony@daylessday.org X-Host-Fingerprint: 89.208.40.236 mail.daylessday.org Linux 2.6 Received: from [89.208.40.236] ([89.208.40.236:50151] helo=daylessday.org) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 44/24-04075-720B1A84 for ; Tue, 12 Aug 2008 11:45:44 -0400 Received: from [192.168.3.254] (unknown [212.42.62.198]) by daylessday.org (Postfix) with ESMTP id 8FFE9640166; Tue, 12 Aug 2008 19:45:37 +0400 (MSD) Message-ID: <48A1B01E.5020908@daylessday.org> Date: Tue, 12 Aug 2008 19:45:34 +0400 User-Agent: Thunderbird 2.0.0.12 (X11/20071114) MIME-Version: 1.0 To: Marcus Boerger CC: php-dev References: <4892E15D.1080004@daylessday.org> <48A19D61.6080502@daylessday.org> <1461769324.20080812165923@marcus-boerger.de> <48A1A6A4.1050801@daylessday.org> <1257013106.20080812172357@marcus-boerger.de> <48A1ACBC.7020808@daylessday.org> <1466695437.20080812173611@marcus-boerger.de> In-Reply-To: <1466695437.20080812173611@marcus-boerger.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] enabling everything by default From: tony@daylessday.org (Antony Dovgal) On 12.08.2008 19:36, Marcus Boerger wrote: > That would actually be a good thing to do. But seriously we decided to give > Phar a try, so we should stick to that until close to final release. See, that's exactly what I said to Pierre ten minutes ago. We'll keep it enabled until close to the release, but we won't disable it EVER "because it was enabled all the way long and now it's too late" or "it looks stable enough for me". -- Wbr, Antony Dovgal