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 thing to the master branch.
Anyway, it is the past, let's deal with the present issue now.

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!

I got an email from Stas regarding my commits, I replied, but the end result is still like this.

What is the procedure to make sure our latest sapi/litespeed release will be in the next release?

Best regards,
George Wang



--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to