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 l
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 better
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 l
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 Sat
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 and
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 three-
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 thi
On Fri, Jul 25, 2014 at 12:23 AM, George Wang
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 EOL al
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 fixe
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 versi
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.
We had some difficult to commit our LiteSpeed SAPI code into PHP source
repository before, so it is lagging behind our office release.
The sapi/litespeed code in 5.3.28 is
11 matches
Mail list logo
