Mailing-List: contact log4net-dev-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4NET Dev" <log4net-dev@logging.apache.org>
Received-SPF: pass (nike.apache.org: domain of dpsenner@gmail.com designates
 209.85.216.181 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CADVsjzNjX8kyddyL7979Y971=w_iVvtUdXwQ5kGLPoJpeeutOg@mail.gmail.com>
References: 
 <CADVsjzNjX8kyddyL7979Y971=w_iVvtUdXwQ5kGLPoJpeeutOg@mail.gmail.com>
Date: Fri, 9 Aug 2013 19:00:48 +0200
Message-ID: 
 <CA+0K2P8fzgindaO2eOmiBV4w=4gD=6o0Shwnvg3fEe5wu7pNEA@mail.gmail.com>
Subject: Re: Creating a development environment for resolving LOG4NET-367
From: Dominik Psenner <dpsenner@gmail.com>
To: Log4NET Dev <log4net-dev@logging.apache.org>
Content-Type: multipart/alternative; boundary=047d7bd766de5e15f404e386b7bb

--047d7bd766de5e15f404e386b7bb
Content-Type: text/plain; charset=ISO-8859-1

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  #
##########################################################

--047d7bd766de5e15f404e386b7bb
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Howdie,<div><br></div><div>the patch there is mainly a fir=
st implementation showing the road we would like to go. There are many thin=
gs to be discussed and I would start with paperizing the ideas before start=
ing the implementation. The reimplementation should solve all known current=
 issues of the rolling file appender.</div>
<div><br></div><div>The patches repository is nothing else than a repositor=
y that holds patches that can be applied to the log4net source, which is lo=
cated at <a href=3D"http://apache.org">apache.org</a>&#39;s svn. It&#39;s t=
here to materialize the ideas without requiring write permissions to the ac=
tual svn and can be used as a sandbox to play with ideas.</div>
<div><br></div><div>I started off with an implementation as a patch and wan=
ted to improve that patch until it is stable enough to join the log4net app=
enders in svn.</div><div><br></div><div>Cheers</div></div><div class=3D"gma=
il_extra">
<br><br><div class=3D"gmail_quote">2013/8/9 d_k <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:mail4dk@gmail.com" target=3D"_blank">mail4dk@gmail.com</a>&gt;=
</span><br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bor=
der-left:1px #ccc solid;padding-left:1ex">
<div dir=3D"ltr">Hi,<br><br>So I think I got a working development environm=
ent for log4net.<br><br>I
 installed mercurial and forked the log4net-crew repository (<a href=3D"htt=
ps://bitbucket.org/NachbarsLumpi/log4net-crew" target=3D"_blank">https://bi=
tbucket.org/NachbarsLumpi/log4net-crew</a>) and the log4net-patches reposit=
ory (<a href=3D"https://bitbucket.org/NachbarsLumpi/log4net-patches" target=
=3D"_blank">https://bitbucket.org/NachbarsLumpi/log4net-patches</a>) and ap=
plied the RFA-NG patch with &#39;hg import&#39;.<br>

<br>Should I prefer to use <a href=3D"http://svn.apache.org/viewvc/logging/=
log4net/trunk" target=3D"_blank">http://svn.apache.org/viewvc/logging/log4n=
et/trunk</a> over <a href=3D"https://bitbucket.org/NachbarsLumpi/log4net-cr=
ew" target=3D"_blank">https://bitbucket.org/NachbarsLumpi/log4net-crew</a>?=
 Will svn and mercurial coexist peacefully?<br>


<br>Do I need anything else to start developing?<br><br>Should I create my =
own RFA-NG2 patch? Or perhaps RFA-NG-NNN for each bug in the supercedes lis=
t of LOG4NET-367 (<a href=3D"https://issues.apache.org/jira/browse/LOG4NET-=
367" target=3D"_blank">https://issues.apache.org/jira/browse/LOG4NET-367</a=
>)?<br>

<br>Are there any common pitfalls I should avoid?</div>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>Dominik Psen=
ner<br>## OpenPGP Key Signature #################################<br># Key =
ID: B469318C=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 =A0 =A0=A0 #<br># Fingerprint: 558641995F7EC2D251354C3A49C7E3D1B469318=
C=A0 #<br>
##########################################################<br><br>
</div>

--047d7bd766de5e15f404e386b7bb--