Guten Tag Roland,
am Freitag, 9. März 2012 um 08:44 schrieben Sie:
> The patch named log4cxx-385 has waited in bug-repository for a long
> time (more than a year), no-one has committed it.
There was a discussion about if the project is still alive and a fork
was initiated. Maybe you want to publi
Hi.
I appreciate your try to make a fork but there are a few things on my
mind before I'd commit there.
1. There already exists a project named log4cpp
http://log4cpp.sourceforge.net/
so the name is a bit misleading
2. You did not include old changelog, which is available at
https://githu
hi all,
i think its better to continue with https://github.com/apache/log4cxx
repo. Since it has change log, we can go ahead with committing bug fixes.
But i wonder which has the latest code.
On Fri, Mar 9, 2012 at 2:59 PM, Roland wrote:
> Hi.
>
> I appreciate your try to make a fork but th
Guten Tag chand priyankara,
am Freitag, 9. März 2012 um 12:31 schrieben Sie:
> i think its better to continue with https://github.com/apache/log4cxx
> repo. Since it has change log, we can go ahead with committing bug fixes.
But currently nobody is (able to) commiting, that's the problem. ;-)
M
Hi.
Since I'm unable to commit to the original project, I forked it, and
committed the LOGCXX-385 patch.
You can pull the fix, if you ever have time.
PS. Palic, Darko if we all fork the original project (
https://github.com/apache/log4cxx ), then github will remember the
forking, and it wil
