Re: svn: /php/php-src/ branches/PHP_5_4/ext/zlib/zlib.c trunk/ext/zlib/zlib.c
| From: | Philip Olson | Date: | Wed, 07 Mar 2012 17:19:12 +0000 |
| Subject: | Re: svn: /php/php-src/ branches/PHP_5_4/ext/zlib/zlib.c trunk/ext/zlib/zlib.c | ||
| References: | 1 2 | Groups: | php.cvs |
| Request: | Send a blank email to php-cvs+get-67865@lists.php.net to get a copy of this message | ||
On Mar 7, 2012, at 8:15 AM, Christopher Jones wrote:
>
>
> On 3/7/12 12:51 AM, Gustavo André dos Santos Lopes wrote:
>> cataphract Wed, 07 Mar 2012 08:51:30 +0000
>>
>> Revision:
>> http://svn.php.net/viewvc?view=revision&revision=323988
>>
>> Log:
>> - Tentative fix for bug #61306.
>> #cjones: Will update NEWS when confirmed it fixes the problem.
>>
>> Bug: https://bugs.php.net/61306 (Assigned) Segfault at end
>> of request
>>
>> Changed paths:
>> U php/php-src/branches/PHP_5_4/ext/zlib/zlib.c
>> U php/php-src/trunk/ext/zlib/zlib.c
>>
>
> LOL! My gut feel says that NEWS should be kept in sync whenever code
> changes. It doesn't seem technically difficult. Keeping NEWS up to
> date avoids any bus-factor or memory-loss situations. If a bug fix is
> reverted, it's trivial to update NEWS again. NEWS comments can say
> "attempt to fix" or "unfinished" if there is some temporary
> uncertainty about a fix.
They don't call him Christopher NEWS Jones for nothin'. :)