logging-log4net-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dominik Psenner <dpsen...@gmail.com>
Subject Re: Creating a development environment for resolving LOG4NET-367
Date Fri, 09 Aug 2013 17:00:48 GMT
Howdie,

the patch there is mainly a first implementation showing the road we would
like to go. There are many things to be discussed and I would start with
paperizing the ideas before starting the implementation. The
reimplementation should solve all known current issues of the rolling file
appender.

The patches repository is nothing else than a repository that holds patches
that can be applied to the log4net source, which is located at apache.org's
svn. It's there to materialize the ideas without requiring write
permissions to the actual svn and can be used as a sandbox to play with
ideas.

I started off with an implementation as a patch and wanted to improve that
patch until it is stable enough to join the log4net appenders in svn.

Cheers


2013/8/9 d_k <mail4dk@gmail.com>

> Hi,
>
> So I think I got a working development environment for log4net.
>
> I installed mercurial and forked the log4net-crew repository (
> https://bitbucket.org/NachbarsLumpi/log4net-crew) and the log4net-patches
> repository (https://bitbucket.org/NachbarsLumpi/log4net-patches) and
> applied the RFA-NG patch with 'hg import'.
>
> Should I prefer to use http://svn.apache.org/viewvc/logging/log4net/trunkover
> https://bitbucket.org/NachbarsLumpi/log4net-crew? Will svn and mercurial
> coexist peacefully?
>
> Do I need anything else to start developing?
>
> Should I create my own RFA-NG2 patch? Or perhaps RFA-NG-NNN for each bug
> in the supercedes list of LOG4NET-367 (
> https://issues.apache.org/jira/browse/LOG4NET-367)?
>
> Are there any common pitfalls I should avoid?
>



-- 
Dominik Psenner
## OpenPGP Key Signature #################################
# Key ID: B469318C                                       #
# Fingerprint: 558641995F7EC2D251354C3A49C7E3D1B469318C  #
##########################################################

Mime
View raw message