Index: cvs-howto.txt
===================================================================
RCS file: /cvsroot/mplayer/main/DOCS/tech/cvs-howto.txt,v
retrieving revision 1.22
diff -u -r1.22 cvs-howto.txt
--- cvs-howto.txt	20 Apr 2005 20:22:57 -0000	1.22
+++ cvs-howto.txt	21 Aug 2005 12:19:35 -0000
@@ -182,6 +182,31 @@
    changed and why. You can refer to mailing list postings if you fix a
    particular bug. Comments such as "fixed!" or "Changed it." are unacceptable.
 
+   A commit message should at least contain:
+   
+   * A high level description of what the change does (fixes calculation of...).
+   * A low level description, summary of the diff (int/int does not produce...).
+   * A list of bug numbers, mailinglist archive links together with the
+     Message-ID's of the mails of the bugs fixed
+     (fixes bug #23, 
+     http://www.mplayerhq.hu/pipermail/mplayer-users/2005-August/055157.html,
+     Message-ID: <43084FB4.2090303@poczta.onet.pl>).
+   * A description of possible unwanted side effects (might not work in case X).
+   * A summary of performed tests and benchmarks.
+   * Severity of the bug/change.
+   * One or more of the tags of:
+       - cosmetic
+       - crash-fix
+       - rounding-fix
+       - security-fix
+       - spelling-fix
+       - indention-fix
+       - untested
+       - new-feature
+       - optimization
+     marked with the keyword "TAGS:" in the first line of the commit message
+     (eg "TAGS: new-feature, untested").
+
 8. If you apply a patch by someone else, include the name and email address in
    the CVS log message. Since the mplayer-cvslog mailing list is publicly
    archived you should add some spam protection to the email address. Send an