You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4php-dev@logging.apache.org by Rotem Erlich <ro...@rotium.com> on 2009/02/07 16:39:51 UTC

Re: Current state of log4php

Littel patch that fix loading configuration file.

Rotem.

-----Original Message-----
From: Jim Jagielski <ji...@jaguNET.com>
To: Log4PHP Dev <lo...@logging.apache.org>
Subject: Re: Current state of log4php
Date: Tue, 20 Jan 2009 18:46:23 -0500

I'm open to champion any patches that come in...

On Jan 20, 2009, at 3:02 AM, Christian Grobmeier wrote:

> Thanks for your answers.
> I believe the code is good, but nothing seems to change. Having the
> email of Marshall in mind, it looks like he felt to make a fork to get
> his changes in and this means, there is space for improvement. To be
> honest, log4php looks a bit dead at the moment. And this is a sad
> thing - i am also trying to get my php project incubated and I hoped
> that here is more community action.
>
> On Fri, Jan 16, 2009 at 9:18 PM, Jim Jagielski <ji...@jagunet.com>  
> wrote:
>> There is not much activity at all. It doesn't mean that the
>> code sucks, it just means that it does what it should
>> do and there hasn't been any real push to add more...
>>
>> On Jan 16, 2009, at 1:50 AM, Christian Grobmeier wrote:
>>
>>> Hi there,
>>>
>>> is there anybody working on log4php?
>>>
>>> Best,
>>> Christian
>>>
>>
>>
>


Re: Current state of log4php

Posted by Jim Jagielski <ji...@jaguNET.com>.
Thanks... Since parse_ini_file returns an array, your
patch is better.
On Feb 7, 2009, at 10:39 AM, Rotem Erlich wrote:

> Littel patch that fix loading configuration file.
>
> Rotem.
>
> -----Original Message-----
> From: Jim Jagielski <ji...@jaguNET.com>
> To: Log4PHP Dev <lo...@logging.apache.org>
> Subject: Re: Current state of log4php
> Date: Tue, 20 Jan 2009 18:46:23 -0500
>
> I'm open to champion any patches that come in...
>
> On Jan 20, 2009, at 3:02 AM, Christian Grobmeier wrote:
>
> > Thanks for your answers.
> > I believe the code is good, but nothing seems to change. Having the
> > email of Marshall in mind, it looks like he felt to make a fork to  
> get
> > his changes in and this means, there is space for improvement. To be
> > honest, log4php looks a bit dead at the moment. And this is a sad
> > thing - i am also trying to get my php project incubated and I hoped
> > that here is more community action.
> >
> > On Fri, Jan 16, 2009 at 9:18 PM, Jim Jagielski <ji...@jagunet.com>
> > wrote:
> >> There is not much activity at all. It doesn't mean that the
> >> code sucks, it just means that it does what it should
> >> do and there hasn't been any real push to add more...
> >>
> >> On Jan 16, 2009, at 1:50 AM, Christian Grobmeier wrote:
> >>
> >>> Hi there,
> >>>
> >>> is there anybody working on log4php?
> >>>
> >>> Best,
> >>> Christian
> >>>
> >>
> >>
> >
>
> <patch.txt>