/[gentoo-x86]/skel.ChangeLog
Gentoo

Diff of /skel.ChangeLog

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

Revision 1.6 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.6 2002/07/09 21:26:08 blizzy 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 DD MMM YYYY; YOUR_NAME <YOUR_EMAIL> changed_file1, changed_file2: 7 DD MMM YYYY; YOUR_NAME <YOUR_EMAIL> changed_file1, changed_file2:
8 8
9 Initial import. 9 Initial import.
10 ebuild submitted by submitter_name <submitter_email>
10 11
11 12
12-- Explanation of ChangeLog format: 13-- Explanation of ChangeLog format:
13 14
14 This changelog is targetted to users. This means that the comments should be 15 This changelog is targetted to users. This means that the comments should be
26 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
27 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
28 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
29 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
30 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.6  
changed lines
  Added in v.1.7

  ViewVC Help
Powered by ViewVC 1.1.20