/[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.8
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.8 2002/07/16 20:30:57 drobbins 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: Initial
8 import. Ebuild submitted by submitter_name <submitter_email>. Note that the
9 "changed_file" listing is optional if you are simply bumping the rev of the
10 ebuild and are only making changes to the .ebuild file itself. Also note
11 that we now have a single unified paragraph rather than having the first line
12 separated from the rest by a newline. Everything should be in one block like
13 this. (note by drobbins, 16 Jul 2002)
8 14
9 Initial import. 15 DD MMM YYYY; YOUR_NAME <YOUR_EMAIL> changed_file1, changed_file2: this is
10 16 an earlier ChangeLog enty.
11 17
12-- Explanation of ChangeLog format: 18-- Explanation of ChangeLog format:
13 19
14 This changelog is targetted to users. This means that the comments should be 20 This changelog is targetted to users. This means that the comments should be
15 well explained and written in clean English. 21 well explained and written in clean English.
26 explanation should follow. It should be indented and wrapped at a line width 32 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 33 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 34 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 35 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. 36 added as a message when the changes are committed to cvs, not in this file.
37
38-- A word regarding credit:
39
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.
43
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.

Legend:
Removed from v.1.6  
changed lines
  Added in v.1.8

  ViewVC Help
Powered by ViewVC 1.1.20