Hi Ferenc,
is there any reason why seemingly you never read my original mail
about those branches beeing off-limit and those commit gonna be reverted?
http://news.php.net/php.cvs/79411
That's my fault due to how my email filters was configured.
Just a suggestion to make the collaboration
Hi,
Hi!
All right, looks like it is my fault not making the reply sounds
critical enough. It pretty much make all third party php-litespeed rpms
useless, only causes trouble and confusion for LiteSpeed users.
I'm not sure what changed with the last php release - the old code was
there for a
as I mentioned previously when you reported the issue, based on the
push reject message, you were trying to push to a subdirectory, where
you didn't have access (probably had something not merged upwards in
Zend/ or similar).
All my changes were under sapi/litespeed directory, did the same
Hi!
I just found that my commits to PHP-5.4.31 and PHP-5.5.15 branch have
been voided, the result is that in final 5.4.31 and 5.5.15 release
package, sapi/litespeed code is still the ancient V5.5 release, it is
ridiculous!
No, it is not ridiculous, it is the release process. The
All right, looks like it is my fault not making the reply sounds
critical enough. It pretty much make all third party php-litespeed rpms
useless, only causes trouble and confusion for LiteSpeed users.
Maybe the release branches should be only open to the RMs, save everyone
time and efforts
Hi George,
is there any reason why seemingly you never read my original mail about
those branches beeing off-limit and those commit gonna be reverted?
http://news.php.net/php.cvs/79411
ps: we prefer bottom-posting on the php.net lists, and that hasn't changed
in the last couple of years.
On
Hi!
All right, looks like it is my fault not making the reply sounds
critical enough. It pretty much make all third party php-litespeed rpms
useless, only causes trouble and confusion for LiteSpeed users.
I'm not sure what changed with the last php release - the old code was
there for a
On Wed, 2014-07-23 at 18:22 -0400, George Wang wrote:
Hi,
I have a request to include our latest sapi/litespeed V6.6 to the EOL
PHP 5.3 release. I thought it was EOL already.
PHP 5.3 is in extended support and only receives security related fixes.
In general people should use newer versions
On 7/24/2014 10:40 AM, Johannes Schlüter wrote:
On Wed, 2014-07-23 at 18:22 -0400, George Wang wrote:
Hi,
I have a request to include our latest sapi/litespeed V6.6 to the EOL
PHP 5.3 release. I thought it was EOL already.
PHP 5.3 is in extended support and only receives security related
On Fri, Jul 25, 2014 at 12:23 AM, George Wang gw...@litespeedtech.com
wrote:
On 7/24/2014 10:40 AM, Johannes Schlüter wrote:
On Wed, 2014-07-23 at 18:22 -0400, George Wang wrote:
Hi,
I have a request to include our latest sapi/litespeed V6.6 to the EOL
PHP 5.3 release. I thought it was
Hi!
According to PHP 5.3 EOL RFC, we've now a month past official EOL date,
but we've planned to make one final release incorporating most important
fixes from upper branches since the last 5.3 release. To help with that,
I've created a pull here:
https://github.com/php/php-src/pull/730
Hi,
On Tue, 2014-07-22 at 11:53 -0700, Stas Malyshev wrote:
Hi!
According to PHP 5.3 EOL RFC, we've now a month past official EOL date,
but we've planned to make one final release incorporating most important
fixes from upper branches since the last 5.3 release. To help with that,
I've
On Tue, Jul 22, 2014 at 8:59 PM, Johannes Schlüter johan...@php.net wrote:
Hi,
On Tue, 2014-07-22 at 11:53 -0700, Stas Malyshev wrote:
Hi!
According to PHP 5.3 EOL RFC, we've now a month past official EOL date,
but we've planned to make one final release incorporating most
important
Hi!
Thanks for the work! The list looks good. Any opinions on #67541? WHich
was requested there? going strict by the rules it won't qualify.
In principle, I don't have anything against it but I'm not familiar with
the code there enough to understand the full set of consequences. I'd
like to
Hi!
not sure, have you seen https://bugs.php.net/bug.php?id=67606 ?
This is worrying. Looks like the patch is not as safe as we've hoped,
and causes BC issues for mod_fastcgi, so maybe we should not get it into
5.3. Once it stabilizes, we can backport it into 5.4, but for 5.3 better
safe than
On Tue, 2014-07-22 at 21:05 +0200, Ferenc Kovacs wrote:
Thanks for the work! The list looks good. Any opinions on
#67541? WHich
was requested there? going strict by the rules it won't
qualify.
johannes
not sure, have
On 22 Jul 2014, at 21:10, Stas Malyshev smalys...@sugarcrm.com wrote:
Hi!
not sure, have you seen https://bugs.php.net/bug.php?id=67606 ?
This is worrying. Looks like the patch is not as safe as we've hoped,
and causes BC issues for mod_fastcgi, so maybe we should not get it into
5.3.
On Tue, 2014-07-22 at 21:41 +0200, David Zuelke wrote:
On 22 Jul 2014, at 21:10, Stas Malyshev smalys...@sugarcrm.com wrote:
Hi!
not sure, have you seen https://bugs.php.net/bug.php?id=67606 ?
This is worrying. Looks like the patch is not as safe as we've hoped,
and causes BC
Hi!
According to PHP 5.3 EOL RFC, we've now a month past official EOL date,
but we've planned to make one final release incorporating most important
fixes from upper branches since the last 5.3 release. To help with that,
I've created a pull here:
https://github.com/php/php-src/pull/730
That
19 matches
Mail list logo
