Contents of /skel.ChangeLog

Parent Directory Parent Directory | Revision Log Revision Log

Revision 1.11 - (show annotations) (download)
Mon Feb 17 02:09:27 2003 UTC (17 years, 7 months ago) by vapier
Branch: MAIN
Changes since 1.10: +1 -1 lines

1 # ChangeLog for <CATEGORY>/<PACKAGE_NAME>
2 # Copyright 2000-2003 Gentoo Technologies, Inc.; Distributed under the GPL v2
3 # $Header: $
7 DD MMM YYYY; YOUR_NAME <YOUR_EMAIL> changed_file1, changed_file2 :
8 Initial import. Ebuild submitted by submitter_name <submitter_email>.
9 Note that the "changed_file" listing is optional if you are simply bumping
10 the rev of the ebuild and are only making changes to the .ebuild file
11 itself. Also note that we now have a single unified paragraph rather than
12 having the first line separated from the rest by a newline. Everything
13 should be in one block like this. (note by drobbins, 16 Jul 2002)
15 DD MMM YYYY; YOUR_NAME <YOUR_EMAIL> changed_file1, changed_file2: this is
16 an earlier ChangeLog enty.
18 -- Explanation of ChangeLog format:
20 This changelog is targetted to users. This means that the comments should be
21 well explained and written in clean English.
23 Every new version or revision of the package should be marked by a '*'
24 seperator line as above. Changes since the last revision have to be added to
25 the top of the file, underneath the initial copyright and cvs header
26 comments, in exactly the same format as this comment.
28 This means that you start with header line that has the following format,
29 indented two spaces:
31 DD MMM YYYY; your_name <your_email> changed_file1, changed_file2: Your
32 explanation should follow. It should be indented and wrapped at a line width
33 of 80 characters. The changed_files can be omitted if they are obvious; for
34 example, if you are only modifying the .ebuild file and committing a new rev
35 of a package. Any details about what exactly changed in the code should be
36 added as a message when the changes are committed to cvs, not in this file.
38 -- A word regarding credit:
40 Please add credit information ("ebuild submitted by ...", "patch submitted
41 by ...") to the ChangeLog. Do not add this information to the ebuilds
42 themselves.
44 And remember: Give credit where credit is due. We're all doing this for
45 free, so the best we can hope (and expect!) to receive is credit.

  ViewVC Help
Powered by ViewVC 1.1.20