summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorStuart Bouyer <stubear@gentoo.org>2002-06-25 16:01:22 +0000
committerStuart Bouyer <stubear@gentoo.org>2002-06-25 16:01:22 +0000
commit28b515af5c859321ae28d95b44706d7224180cc1 (patch)
tree46dc7c5cf214dd1f6ea980c96dfe137c663a76a7 /x11-terms/hanterm/ChangeLog
parent*gaim-0.58-r3 (26 June 2002) (diff)
downloadhistorical-28b515af5c859321ae28d95b44706d7224180cc1.tar.gz
historical-28b515af5c859321ae28d95b44706d7224180cc1.tar.bz2
historical-28b515af5c859321ae28d95b44706d7224180cc1.zip
New Changelog added 26 June 2002
Diffstat (limited to 'x11-terms/hanterm/ChangeLog')
-rw-r--r--x11-terms/hanterm/ChangeLog26
1 files changed, 26 insertions, 0 deletions
diff --git a/x11-terms/hanterm/ChangeLog b/x11-terms/hanterm/ChangeLog
new file mode 100644
index 000000000000..a16922bc1e34
--- /dev/null
+++ b/x11-terms/hanterm/ChangeLog
@@ -0,0 +1,26 @@
+# ChangeLog for <CATEGORY>/<PACKAGE_NAME>
+# Copyright 2002 Gentoo Technologies, Inc.; Distributed under the GPL v2
+# $Header: /var/cvsroot/gentoo-x86/x11-terms/hanterm/ChangeLog,v 1.1 2002/06/25 16:01:22 stubear Exp $
+
+*<PACKAGE_NAME>-<PACKAGE_VERSION>-<PACKAGE_RELEASE> (DD MMM YYYY)
+
+ 01 Feb 2002; G.Bevin <gbevin@gentoo.org> skel.ChangeLog: This changelog is
+ targetted to users. This means that the comments should be well explained and
+ written in clean English.
+
+-- Explanation of ChangeLog format:
+
+ Every new version or revision of the package should be marked by a '*'
+ seperator line as above. Changes since the last revision have to be added to
+ the top of the file, underneath the initial copyright and cvs header
+ comments, in exactly the same format as this comment.
+
+ 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
+ example, if you are only modifying the .ebuild file and committing a new rev
+ of a package. Any details about what exactly changed in the code should be
+ added as a message when the changes are committed to cvs, not in this file.