The branch, PHP_POST_RECEIVE on karma.git has been updated
via 46adcc9c1571d5a20660ca49b2762189a1495786 (commit)
from c7163b23683f8656f913ff4d22706ca5a5f41380 (commit)
http://git.php.net/?p=karma.git;a=log;h=46adcc9c1571d5a20660ca49b2762189a1495786;hp=c7163b23683f8656f913ff4d22706ca
The branch, master on karma.git has been updated
via fc9c78fe12aa756060684e565adf8fb8a4373120 (commit)
from c388fdc594d5cf8f8f695eef47c179e2e1acc39e (commit)
http://git.php.net/?p=karma.git;a=log;h=fc9c78fe12aa756060684e565adf8fb8a4373120;hp=c388fdc594d5cf8f8f695eef47c179e2e1acc39e
cataphract Wed, 07 Mar 2012 08:51:30 +
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 en
On 3/6/12 11:49 PM, Stanislav Malyshev wrote:
stas Wed, 07 Mar 2012 07:49:56 +
Revision: http://svn.php.net/viewvc?view=revision&revision=323986
Log:
MFH: Headers: forbid \r and \n also after \0, allow CRLF followed by HT or SP
and forbid \0. See bug
On 3/6/12 11:38 PM, Stanislav Malyshev wrote:
stas Wed, 07 Mar 2012 07:38:57 +
Revision: http://svn.php.net/viewvc?view=revision&revision=323985
Log:
MFH: Fixed bug #61173 (Unable to detect error from finfo constructor).
Bug: https://bugs.php.net/61173
On 3/7/12 12:51 AM, Gustavo André dos Santos Lopes wrote:
cataphract Wed, 07 Mar 2012 08:51:30 +
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 probl
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 +
>>
>> Revision: http://svn.php.net/viewvc?view=revision&revision=323988
>>
>> Log:
>> - Tentative fi
Hi!
What about NEWS?
It's already fixed in 5.3...
--
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227
--
PHP CVS Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
On 03/07/2012 09:51 AM, Stas Malyshev wrote:
Hi!
What about NEWS?
It's already fixed in 5.3...
Urrgh, so it (#60227) is. We need a better branching mechanism so
users can tell what is fixed and what isn't in any particular release.
--
Email: [email protected]
Tel: +1 650 506
On 03/07/2012 08:06 AM, Christopher Jones wrote:
On 3/6/12 11:38 PM, Stanislav Malyshev wrote:
stas Wed, 07 Mar 2012 07:38:57 +
Revision: http://svn.php.net/viewvc?view=revision&revision=323985
Log:
MFH: Fixed bug #61173 (Unable to detect error from finfo constructor).
Bug: https://bu
Hi!
This one (#61173) isn't in 5.4 NEWS, since it was only fixed in 5.3.11.
Do we now duplicate 5.3 and 5.4 NEWS?
--
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227
--
PHP CVS Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www
hi Chris,
Agreed.
I would also like to have entries for what get fixed since the last
release of the same branch. It is even more important with the totally
asynchronous (and somehow slow) 5.3 releases.
On Wed, Mar 7, 2012 at 6:57 PM, Christopher Jones
wrote:
>
>
> On 03/07/2012 09:51 AM, Stas
On 03/07/2012 10:00 AM, Stas Malyshev wrote:
Hi!
This one (#61173) isn't in 5.4 NEWS, since it was only fixed in 5.3.11.
Do we now duplicate 5.3 and 5.4 NEWS?
Users should be able to see the fixes in 5.4 by reading only 5.4 NEWS.
I think the 5.3 & 5.4 branches have to be considered distin
Hi!
Users should be able to see the fixes in 5.4 by reading only 5.4 NEWS.
That's why we merge 5.3 news before the release.
I think the 5.3& 5.4 branches have to be considered distinct from now
on.
What's different now?
--
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugar
I think what Chris is asking is to have NEWS entries in the branch
where a commit is done, no mater if the fix was already reported in a
previous branch NEWS file.
On Wed, Mar 7, 2012 at 7:15 PM, Stas Malyshev wrote:
> Hi!
>
>
>> Users should be able to see the fixes in 5.4 by reading only 5.4 NE
Hi!
I think what Chris is asking is to have NEWS entries in the branch
where a commit is done, no mater if the fix was already reported in a
previous branch NEWS file.
It'd mean instead of easy merge on release we'd have to have hard and
time-consuming cleanup of old NEWS - I'd have to go thr
On Wed, Mar 7, 2012 at 7:22 PM, Stas Malyshev wrote:
> Or we'd just have it twice in both 5.3 and 5.4 sections?
Yes
> BTW, why we don't put the same in the trunk NEWS then?
I would say we could consider to add NEWS entry after a 1st release
for a given branch?
Cheers,
--
Pierre
@pierrejoye
On 03/07/2012 10:22 AM, Stas Malyshev wrote:
Hi!
I think what Chris is asking is to have NEWS entries in the branch
where a commit is done, no mater if the fix was already reported in a
previous branch NEWS file.
It'd mean instead of easy merge on release we'd have to have hard and
time-co
On 03/07/2012 10:15 AM, Stas Malyshev wrote:
Hi!
Users should be able to see the fixes in 5.4 by reading only 5.4 NEWS.
That's why we merge 5.3 news before the release.
See my other email. This is error prone since bugs may not be
relevant, and release cycles may not coincide. I'd like
cataphract Wed, 07 Mar 2012 19:47:18 +
Revision: http://svn.php.net/viewvc?view=revision&revision=324008
Log:
- Updated NEWS with news of bug #61306 having been resolved (see r323988).
- Tidied up NEWS
Bug: https://bugs.php.net/61306 (Assigned) Segfault at end o
iliaaThu, 08 Mar 2012 03:31:46 +
Revision: http://svn.php.net/viewvc?view=revision&revision=324009
Log:
Fixed bug #60634 (Segmentation fault when trying to die() in
SessionHandler::write())
Bug: https://bugs.php.net/60634 (Assigned) Segmentation fault whe
21 matches
Mail list logo
