Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:80161 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 53752 invoked from network); 4 Jan 2015 22:04:29 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Jan 2015 22:04:29 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.218.54 as permitted sender) X-PHP-List-Original-Sender: smalyshev@gmail.com X-Host-Fingerprint: 209.85.218.54 mail-oi0-f54.google.com Received: from [209.85.218.54] ([209.85.218.54:46879] helo=mail-oi0-f54.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 40/76-02442-AE8B9A45 for ; Sun, 04 Jan 2015 17:04:28 -0500 Received: by mail-oi0-f54.google.com with SMTP id u20so45545804oif.13 for ; Sun, 04 Jan 2015 14:04:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=Dk8Jpebn8RE/FeKoTzxosKo9JM70LAAozutzcXL9slo=; b=nfvgdGv54b88uPkKW8hq8w8rHh+eZx9bPoTXJZb/NmryHxNqh/6ckRpiQMn/KYYGLW SOEWsNnPHHNMqqFSnA6987VAnZ8jSkTxKPsqQ+1gnB3XFpa4j78koCtEaFdUpYso2DvE K4dQd6dsKqOYV9MKuXJYe7CRygvWGZcf/HVZeC6CmTjXGVrpCZLoFFQtTrW6gePWaf0V 2lLhzPYqIHrUr/P4EREhKHOG3Y7nqd9vJpJVxlvbBmeo8btcAo4CXAiC5Bcp+prDS5Ts bynB3QWd6aaE9LvkE+BZg1j+SlvehN4EMAY7On/SG+Y5vc3DrNN10GQsTgCDQY+ozIRd 9VrQ== X-Received: by 10.182.18.66 with SMTP id u2mr5091593obd.33.1420409063393; Sun, 04 Jan 2015 14:04:23 -0800 (PST) Received: from Stas-Air.local (108-66-6-48.lightspeed.sntcca.sbcglobal.net. [108.66.6.48]) by mx.google.com with ESMTPSA id a15sm22658268oic.18.2015.01.04.14.04.22 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 04 Jan 2015 14:04:22 -0800 (PST) Message-ID: <54A9B8DA.7040608@gmail.com> Date: Sun, 04 Jan 2015 14:04:10 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Dan Ackroyd CC: Kalle Sommer Nielsen , Internals References: <54A109EB.1000805@gmail.com> <54A1974E.8070007@gmail.com> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Bugfest From: smalyshev@gmail.com (Stanislav Malyshev) Hi! > Would it be appropriate to close issues that are clear, but can easily > be done in userland e.g. https://bugs.php.net/bug.php?id=64639 > > Leaving an issue like that open seems to pretty pointless, even though > it is clear what is being asked. Yes, this one is pretty clearly not going to happen, but in general we should tread lightly here - some ideas that seemed pointless in the past ended up accepted and implemented. So if it's a clear-cut case, it's ok to close but if there's any doubt, better to ask on internals or to let somebody among experienced PHP devs take a look. Having a lot of open feature reqs is ok, it's much less annoying that having a lot of open bugs that nobody looks at. -- Stas Malyshev smalyshev@gmail.com