Re: php interactive shell: save history on SIGINT exit
| From: | Bob Weinand | Date: | Mon, 21 Jul 2014 12:34:29 +0000 |
| Subject: | Re: php interactive shell: save history on SIGINT exit | ||
| References: | 1 2 3 4 5 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-75787@lists.php.net to get a copy of this message | ||
Am 21.7.2014 um 12:52 schrieb Pierre Joye <pierre.php@gmail.com>:
> On Mon, Jul 21, 2014 at 11:50 AM, Dmitry Saprykin
> <saprykin.dmitry@gmail.com> wrote:
>> Ok, I will NOT ))
>> God saves us from bureaucracy
>
> Well, Michael's view is known.
>
> However let me explain what RFCs bring, besides bureaucracy.
>
> - clear identification of use cases, incl. edge cases
> - better design and design reviews
> - documentation, ready to be used by the doc team
>
> I do not know how big such changes will be but I can already see a
> couple of things that may require more than "works for me on my fav
> linux distros" edge cases. :)
>
>>> Yes, please do NOT create a RFC for each and every tiny feature. Just find
>>> someone to review and eventually merge your patch!
>
> --
> Pierre
>
> @pierrejoye | http://www.libgd.org
- Here the use case is very obvious, I don't see what a RFC would make clearer here.
- That it was posted to the mailing list should usually attract enough attention to quickly review
such a small patch.
- Here nothing needs to be documented.
People just should feel free to post it on the mailing list; if it gets controversial, then, why
not, create a RFC.
Bob