/[gentoo-x86]/skel.ChangeLog
Gentoo

Diff of /skel.ChangeLog

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

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

Legend:
Removed from v.1.2  
changed lines
  Added in v.1.3

  ViewVC Help
Powered by ViewVC 1.1.20