skel updates

1 files changed, 20 insertions, 19 deletions

diff --git a/skel.ChangeLog b/skel.ChangeLog
index 6c33a5ae597e..fbb74725e4c9 100644
--- a/skel.ChangeLog
+++ b/skel.ChangeLog
@@ -1,25 +1,26 @@
 # ChangeLog for <CATEGORY>/<PACKAGE_NAME>
-# Copyright 2002 Gentoo Technologies, Inc.; Distributed under the GPL
-# $Header: /home/cvsroot/gentoo-x86/skel.ChangeLog,v 1.1 2002/02/01 21:52:59 gbevin Exp $
+# Copyright 2002 Gentoo Technologies, Inc.; Distributed under the GPL v2
+# $Header: /home/cvsroot/gentoo-x86/skel.ChangeLog,v 1.2 2002/02/05 00:57:47 gbevin Exp $
 
-*<PACKAGE_NAME>-<PACKAGE_VERSION>-<PACKAGE_RELEASE> (<DATE>)
+*<PACKAGE_NAME>-<PACKAGE_VERSION>-<PACKAGE_RELEASE> (DD MMM YYYY)
 
-  1 Feb 2002; G.Bevin <gbevin@gentoo.org> skel.ChangeLog :
-  
-  This changelog is targetted to users. This means that the comments should be
-  well explained and written in clean English. 
-  
-  Every new version or revision of the package has to be marked by a '*'
-  seperator line as above. Changements since the last revision have to be
-  added to the top of the file, underneath the initial copyright and cvs header
+  01 Feb 2002; G.Bevin <gbevin@gentoo.org> skel.ChangeLog: This changelog is
+  targetted to users. This means that the comments should be well explained and
+  written in clean English. 
+ 
+-- Explanation of ChangeLog format:
+ 
+  Every new version or revision of the package should be marked by a '*'
+  seperator line as above. Changes since the last revision have to be added to
+  the top of the file, underneath the initial copyright and cvs header
   comments, in exactly the same format as this comment.
   
-  This means that you start with header line that has the following format :
-  
-      date; your_name <your_email> changed_file1, changed_file2 :
-	  
-  Below that line your explanation should follow. It has to be indented,
-  paragraphed and wrapped at a linewidth of 80 characters.
+  This means that you start with header line that has the following format,
+  indented two spaces:
   
-  Any details about what exactly changed in the code should be added as a
-  message when the changes are committed to cvs, not in this file.
+  DD MMM YYYY; your_name <your_email> changed_file1, changed_file2: Your
+  explanation should follow. It should be indented and wrapped at a line width
+  of 80 characters.  The changed_files can be omitted if they are obvious; for
+  example, if you are only modifying the .ebuild file and committing a new rev
+  of a package.  Any details about what exactly changed in the code should be
+  added as a message when the changes are committed to cvs, not in this file.