/[gentoo-x86]/skel.ChangeLog
Gentoo

Diff of /skel.ChangeLog

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

Revision 1.3 Revision 1.7
1# ChangeLog for <CATEGORY>/<PACKAGE_NAME> 1# ChangeLog for <CATEGORY>/<PACKAGE_NAME>
2# Copyright 2002 Gentoo Technologies, Inc.; Distributed under the GPL v2 2# Copyright 2002 Gentoo Technologies, Inc.; Distributed under the GPL v2
3# $Header: /var/cvsroot/gentoo-x86/skel.ChangeLog,v 1.3 2002/05/07 03:58:19 drobbins Exp $ 3# $Header: /var/cvsroot/gentoo-x86/skel.ChangeLog,v 1.7 2002/07/09 21:29:51 blizzy Exp $
4 4
5*<PACKAGE_NAME>-<PACKAGE_VERSION>-<PACKAGE_RELEASE> (DD MMM YYYY) 5*<PACKAGE_NAME>-<PACKAGE_VERSION>-<PACKAGE_RELEASE> (DD MMM YYYY)
6 6
7 01 Feb 2002; G.Bevin <gbevin@gentoo.org> skel.ChangeLog: This changelog is 7 DD MMM YYYY; YOUR_NAME <YOUR_EMAIL> changed_file1, changed_file2:
8 targetted to users. This means that the comments should be well explained and 8
9 written in clean English. 9 Initial import.
10 ebuild submitted by submitter_name <submitter_email>
11
10 12
11-- Explanation of ChangeLog format: 13-- Explanation of ChangeLog format:
14
15 This changelog is targetted to users. This means that the comments should be
16 well explained and written in clean English.
12 17
13 Every new version or revision of the package should be marked by a '*' 18 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 19 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 20 the top of the file, underneath the initial copyright and cvs header
16 comments, in exactly the same format as this comment. 21 comments, in exactly the same format as this comment.
22 explanation should follow. It should be indented and wrapped at a line width 27 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 28 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 29 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 30 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. 31 added as a message when the changes are committed to cvs, not in this file.
32
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.

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

  ViewVC Help
Powered by ViewVC 1.1.20