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