On 07/10/2010 01:22 AM, Matti Bickel wrote:
Hi,
yet another patch from Ole in a bid to rid the php eclasses from some
long forgotten code. The patches should be self-explanatory - just rip
out everything related to dev-php4 :)
Comments welcome.
The standing policy is still not to
On Sat, Jul 10, 2010 at 09:30:42AM +0300, Petteri RRRty wrote:
On 07/10/2010 01:22 AM, Matti Bickel wrote:
Hi,
yet another patch from Ole in a bid to rid the php eclasses from some
long forgotten code. The patches should be self-explanatory - just rip
out everything related to dev-php4
On 07/10/2010 10:34 AM, Brian Harring wrote:
If people want to allow eclasses to have fluid APIs (specifically
removal of functionality), that's a discussion that needs to start on
the dev level.
Anyone got strong opinions on this one?
The argument was presented a long time before: we
Hi,
yet another patch from Ole in a bid to rid the php eclasses from some
long forgotten code. The patches should be self-explanatory - just rip
out everything related to dev-php4 :)
Comments welcome.
All the work will go into our overlay (slotting branch:
