summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
Diffstat (limited to 'skel.ChangeLog')
-rw-r--r--skel.ChangeLog12
1 files changed, 6 insertions, 6 deletions
diff --git a/skel.ChangeLog b/skel.ChangeLog
index 1f22d1271..461131447 100644
--- a/skel.ChangeLog
+++ b/skel.ChangeLog
@@ -1,5 +1,5 @@
# ChangeLog for <CATEGORY>/<PACKAGE_NAME>
-# Copyright 1999-2006 Gentoo Foundation; Distributed under the GPL v2
+# Copyright 1999-2010 Gentoo Foundation; Distributed under the GPL v2
# $Header: $
*<PACKAGE_NAME>-<PACKAGE_VERSION>-<PACKAGE_RELEASE> (DD MMM YYYY)
@@ -14,7 +14,7 @@
DD MMM YYYY; YOUR_NAME <YOUR_EMAIL> changed_file1, changed_file2: this is
an earlier ChangeLog entry.
-
+
-- Explanation of ChangeLog format:
***************************************************************************
@@ -33,10 +33,10 @@
top of the file like a good boy/girl. Even do this if it's clear that you're
adding an entry to a b0rked ChangeLog.
***************************************************************************
-
+
This changelog is targeted to users. This means that the comments should be
well explained and written in clean English.
-
+
Every new version or revision of the package should be marked by a '*'
separator line as above to indicate where in the chronology it was first
added to our CVS tree. Any changes since the last revision, really _any
@@ -46,10 +46,10 @@
files and add your entry to the top of the ChangeLog. Resist the temptation
to "organize" your ChangeLog entries by placing them under the "correct" "*"
entries -- this isn't the purpose of the "*" entries.
-
+
This means that you start with header line that has the following format,
indented two spaces:
-
+
DD MMM YYYY; your_name <your_email> changed_file1, changed_file2: Your
explanation should follow. It should be indented and wrapped at a line width
of 80 characters. The changed_files can be omitted if they are obvious; for