/[gentoo-x86]/skel.ChangeLog
Gentoo

Contents of /skel.ChangeLog

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.7 - (hide annotations) (download)
Tue Jul 9 21:29:51 2002 UTC (13 years, 1 month ago) by blizzy
Branch: MAIN
Changes since 1.6: +10 -0 lines
added credit section

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 blizzy 1.6 DD MMM YYYY; YOUR_NAME <YOUR_EMAIL> changed_file1, changed_file2:
8 blizzy 1.5
9     Initial import.
10 blizzy 1.7 ebuild submitted by submitter_name <submitter_email>
11 blizzy 1.5
12 drobbins 1.3
13     -- Explanation of ChangeLog format:
14 blizzy 1.5
15     This changelog is targetted to users. This means that the comments should be
16     well explained and written in clean English.
17 drobbins 1.3
18     Every new version or revision of the package should be marked by a '*'
19     seperator line as above. Changes since the last revision have to be added to
20     the top of the file, underneath the initial copyright and cvs header
21 gbevin 1.2 comments, in exactly the same format as this comment.
22 gbevin 1.1
23 drobbins 1.3 This means that you start with header line that has the following format,
24     indented two spaces:
25 gbevin 1.1
26 drobbins 1.3 DD MMM YYYY; your_name <your_email> changed_file1, changed_file2: Your
27     explanation should follow. It should be indented and wrapped at a line width
28     of 80 characters. The changed_files can be omitted if they are obvious; for
29     example, if you are only modifying the .ebuild file and committing a new rev
30     of a package. Any details about what exactly changed in the code should be
31     added as a message when the changes are committed to cvs, not in this file.
32 blizzy 1.7
33     -- A word regarding credit:
34    
35     Please add credit information ("ebuild submitted by ...", "patch submitted
36     by ...") to the ChangeLog. Do not add this information to the ebuilds
37     themselves.
38    
39     And remember: Give credit where credit is due. We're all doing this for
40     free, so the best we can hope (and expect!) to receive is credit.

  ViewVC Help
Powered by ViewVC 1.1.20