Folks who are maintaining log4cxx branches at github.com, don't forget to look
at the network graph for the project --- you may find that the fix you need has
already been implemented on another branch.
On 03/09/2012 07:24 AM, Roland wrote:
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 will be really easy to pull changes from each others public repositories.
And the original ASF people can pull the changes they feel are good enough
for them.
Regards,
Roland
On 03/09/2012 01:31 PM, chand priyankara wrote:
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.
