Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:96451
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmx.de designates 212.227.15.15 as permitted sender)
To: Yasuo Ohgaki <yohgaki@php.net>,
 "internals@lists.php.net" <internals@lists.php.net>
References: <CAGa2bXbUmRZ8EK4HB=WyKLK5EcACXZ_wisH1v3=2ib81-HetUQ@mail.gmail.com>
Message-ID: <6f5a9fc2-6eb7-0be0-4aa3-5d25148b7c7a@gmx.de>
Date: Wed, 19 Oct 2016 01:10:04 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101
 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <CAGa2bXbUmRZ8EK4HB=WyKLK5EcACXZ_wisH1v3=2ib81-HetUQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Subject: Re: Bug fix and RFC/Merge rule
From: cmbecker69@gmx.de ("Christoph M. Becker")

Hi Yasuo!

On 18.10.2016 at 23:41, Yasuo Ohgaki wrote:

> After all, my question is "Should we discuss all bugs before commits?"

No, I don't think that would be reasonable for time reasons.  However,
if someone steps in, raising doubts about a certain bug fix, that has to
be discussed and if no consensus can be found, an RFC seems to be the
most sensible way to resolve the issue.  Until the RFC has been decided
upon, (temporarily) reverting the commit also makes sense, in my
opinion. :-)

-- 
Christoph M. Becker