viewvc.cgi/gentoo-x86/skel.ChangeLog

# ChangeLog for <CATEGORY>/<PACKAGE_NAME>
# Copyright 2002 Gentoo Technologies, Inc.; Distributed under the GPL
# $Header: $

*<PACKAGE_NAME>-<PACKAGE_VERSION>-<PACKAGE_RELEASE> (<DATE>)

  1 Feb 2002; G.Bevin <gbevin@gentoo.org> skel.ChangeLog :
  
  This changelog is targetted to users. This means that the comments should 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 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.
  
  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.
1	gbevin	1.1	# ChangeLog for <CATEGORY>/<PACKAGE_NAME>
2			# Copyright 2002 Gentoo Technologies, Inc.; Distributed under the GPL
3			# $Header: $
4
5			*<PACKAGE_NAME>-<PACKAGE_VERSION>-<PACKAGE_RELEASE> (<DATE>)
6
7			1 Feb 2002; G.Bevin <gbevin@gentoo.org> skel.ChangeLog :
8
9			This changelog is targetted to users. This means that the comments should well
10			explained and written in clean English.
11
12			Every new version or revision of the package has to be marked by a '*'
13			seperator line as above. Changements since the last revision have to be
14			added to the top of the file, underneath the initial comments, in exactly the
15			same format as this comment.
16
17			This means that you start with header line that has the following format :
18
19			date; your_name <your_email> changed_file1, changed_file2 :
20
21			Below that line your explanation should follow. It has to be indented,
22			paragraphed and wrapped at a linewidth of 80 characters.
23
24			Any details about what exactly changed in the code should be added as a
25			message when the changes are committed to cvs, not in this file.