mplemented in the patch, but there are
several things that are not yet finished.
Von: Dominik Psenner [mailto:dpsen...@gmail.com]
Gesendet: Sonntag, 11. August 2013 22:59
An: Log4NET Dev
Betreff: Re: Creating a development environment for resolving LOG4NET-367
This is something that wouldn&
This is something that wouldn't work right now:
C:/fancydirectory/%processid/%username/%year/%month/mylogfile.log
inter-process
C:/fancydirectory/%processid/%username/%year/%month/%filenumber/mylogfile.log
but we want it to work in the future. Of couse the syntax may be different,
See the inlines..
2013/8/10 d_k
> Paperizing ideas sounds good. How does the log4net project handle
> requirements? JIRA?
>
Yes
> Are there any requirements other than the ones under the 'supercedes' list?
>
Yes and no. It should be a rolling file appender that handles things
smarter than th
Paperizing ideas sounds good. How does the log4net project handle
requirements? JIRA?
Are there any requirements other than the ones under the 'supercedes' list?
I'm afraid I don't have a 'vision' for the RFA-NG but I think we can take
the patch under log4net-patches, make sure to fix the 'superce
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
append
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 patc
