Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:53736 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 31425 invoked from network); 3 Jul 2011 20:43:07 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 3 Jul 2011 20:43:07 -0000 Authentication-Results: pb1.pair.com header.from=tony@daylessday.org; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=tony@daylessday.org; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain daylessday.org designates 95.163.84.66 as permitted sender) X-PHP-List-Original-Sender: tony@daylessday.org X-Host-Fingerprint: 95.163.84.66 mail.daylessday.org Received: from [95.163.84.66] ([95.163.84.66:45950] helo=daylessday.org) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 92/B1-17862-654D01E4 for ; Sun, 03 Jul 2011 16:43:05 -0400 Received: from thinkx201.site (95-27-190-48.broadband.corbina.ru [95.27.190.48]) by daylessday.org (Postfix) with ESMTPSA id C2B51E3623 for ; Mon, 4 Jul 2011 00:43:00 +0400 (MSD) Message-ID: <4E10D453.9060606@daylessday.org> Date: Mon, 04 Jul 2011 00:42:59 +0400 User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110414 SUSE/3.1.10 Thunderbird/3.1.10 MIME-Version: 1.0 To: internals@lists.php.net References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Big patch for FPM (config and initialization) From: tony@daylessday.org (Antony Dovgal) On 07/03/2011 04:50 AM, Giovanni Giacobbi wrote: > Detailed changelog of the patch: > - Renamed options "pm.status_path", "ping.path", "ping.response" into > a new logical group "diagnostics", so they are now respectively: > "diagnostics.status_path", "diagnostics.ping_path", > "diagnostics.ping_response". I'm not quite sure renaming config options would help anybody, in my opinion it would do more harm than good. I personally would certainly expect my existing config files to continue to work after upgrade to 5_4. Yes, we're changing '3' to '4' in the version number, but that doesn't mean we can just go ahead and break the config file. Other than that, looks ok to me (assuming you've tested it and does continue to work the way it worked before all those cosmetic changes). -- Wbr, Antony Dovgal --- http://pinba.org - realtime profiling for PHP