[ 
http://issues.apache.org/jira/browse/LOG4NET-64?page=comments#action_12368433 ] 

Ron Grabowski commented on LOG4NET-64:
--------------------------------------

I wasn't able to apply this patch with TSVN (TortoiseSVN 1.3.2, Build 5840). 
TSVN requires the header to be in this format:

Index: RollingFileAppender.cs
===================================================================
--- RollingFileAppender.cs      (revision 381326)
+++ RollingFileAppender.cs      (working copy)

After downloading the file (with FireFox, IE6, and wget) and correcting the 
header, I get the following error:

 "An unknown line type was found in line 5 !"

This is line 5:

                        set { m_staticLogFileName = value; }

Maybe Joshua could .zip the patch?

> [PATCH] to RollingFileAppender.cs to add the ability to preserve the log file 
> name extension when rolling the log file.
> -----------------------------------------------------------------------------------------------------------------------
>
>          Key: LOG4NET-64
>          URL: http://issues.apache.org/jira/browse/LOG4NET-64
>      Project: Log4net
>         Type: New Feature
>   Components: Appenders
>     Versions: 1.2.9
>     Reporter: Joshua Bassett
>  Attachments: patch.txt
>
> Normally, when the log file is rolled the file name extension is not 
> preserved.
> For example, file.log is rolled to file.log.1 or file.log.yyyy-MM-dd.
> However, this may not be desired in all cases and it may be necessary to 
> preserve the log file name extension when the log file is rolled. Most 
> notably, this feature is useful for maintaining file associations under 
> Windows so that all log files can be associated with a particaular text 
> viewer.
> For example, file.log is rolled to file.1.log or file.yyyy-MM-dd.log.
> This patch adds an additional boolean property PreserveLogFileNameExtension 
> to the RollingFileAppender class which is used to toggle this behavior.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

Reply via email to