You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4cxx-dev@logging.apache.org by Roland <ro...@gmail.com> on 2012/03/09 10:29:21 UTC
Re: Is log4cxx still alive?
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://github.com/apache/log4cxx
A thing about log4net
It seems less cross-plaform than log4cxx, and seems to be harder to use
on an embedded device.
Since ASF members do not want to maintain this software, like is visible
from here.. https://issues.apache.org/jira/browse/LOGCXX-385 (a patch to
fix a issue)
I think the best idea would be to create a fork of that
https://github.com/apache/log4cxx GIT repository.
I think old commit history with the bugs that were fixed is necessary
for a forked project.
Thanks,
Roland
Re: Is log4cxx still alive?
Posted by Thorsten Schöning <ts...@am-soft.de>.
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. ;-)
Mit freundlichen Grüßen,
Thorsten Schöning
--
Thorsten Schöning E-Mail:Thorsten.Schoening@AM-SoFT.de
AM-SoFT IT-Systeme http://www.AM-SoFT.de/
Telefon.............030-2 1001-310
Fax...............05151- 9468- 88
Mobil..............0178-8 9468- 04
AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hanover HRB 207 694 - Geschäftsführer: Andreas Muchow
Re: Is log4cxx still alive?
Posted by "Nathaniel W. Turner" <na...@houseofnate.net>.
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.
>>
Re: Is log4cxx still alive?
Posted by Roland <ro...@gmail.com>.
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.
>
Re: Is log4cxx still alive?
Posted by chand priyankara <ch...@engineering.com>.
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 <ro...@gmail.com> wrote:
> 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/ <http://log4cpp.sourceforge.net/>
> so the name is a bit misleading
>
> 2. You did not include old changelog, which is available at
> https://github.com/apache/**log4cxx <https://github.com/apache/log4cxx>
>
>
> A thing about log4net
>
> It seems less cross-plaform than log4cxx, and seems to be harder to use on
> an embedded device.
>
>
> Since ASF members do not want to maintain this software, like is visible
> from here.. https://issues.apache.org/**jira/browse/LOGCXX-385<https://issues.apache.org/jira/browse/LOGCXX-385>(a patch to fix a issue)
>
> I think the best idea would be to create a fork of that
> https://github.com/apache/**log4cxx <https://github.com/apache/log4cxx>GIT repository.
>
> I think old commit history with the bugs that were fixed is necessary for
> a forked project.
>
> Thanks,
> Roland
>
--
*Chand Priyankara*
|(094) 773-361566
|chand@engineering.com
|www.blog.friendly.com
[image: Facebook] <http://www.facebook.com/chand.priyankara> [image:
LinkedIn] <http://lk.linkedin.com/in/chandpriyankara> [image:
Blogger]<http://chandpriyankara.blogspot.com/>
[image: Google Plus] <http://plus.google.com/104246340732624023499>
<http://www.iucnredlist.org/amazing-species>
Please consider your environmental responsibility. Before printing this
e-mail message, ask yourself whether you really need a hard copy.
*
*