You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-cvs@jakarta.apache.org by pa...@apache.org on 2001/02/28 21:39:44 UTC
cvs commit: jakarta-log4j/org/apache/log4j RollingFileAppender.java
pathos 01/02/28 12:39:44
Modified: org/apache/log4j RollingFileAppender.java
Log:
Documentation changes.
Revision Changes Path
1.5 +2 -2 jakarta-log4j/org/apache/log4j/RollingFileAppender.java
Index: RollingFileAppender.java
===================================================================
RCS file: /home/cvs/jakarta-log4j/org/apache/log4j/RollingFileAppender.java,v
retrieving revision 1.4
retrieving revision 1.5
diff -u -r1.4 -r1.5
--- RollingFileAppender.java 2001/02/20 19:16:54 1.4
+++ RollingFileAppender.java 2001/02/28 20:39:43 1.5
@@ -111,7 +111,7 @@
}
/**
- Implemetns the usual roll over behaviour.
+ Implements the usual roll over behaviour.
<p>If <code>MaxBackupIndex</code> is positive, then files
{<code>File.1</code>, ..., <code>File.MaxBackupIndex -1</code>}
@@ -200,7 +200,7 @@
as 10240.
<p>The <b>MaxBackupIndex</b> option determines how many backup
- files are kept before the oldest being erased. This option takes
+ files are kept before the oldest is erased. This option takes
a positive integer value. If set to zero, then there will be no
backup files and the log file will be truncated when it reaches
<code>MaxFileSize</code>.