From: Yasuo Ohgaki <yohgaki@php.net>
Date: Thu, 28 Feb 2002 06:21:09 +0000 (+0000)
Subject: Added how to put bug ID in commit message.
X-Git-Tag: php-4.2.0RC1~254
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=1c12a65f826def825413fea38c21f9b2cd00f8e8;p=php

Added how to put bug ID in commit message.
---

diff --git a/README.CVS-RULES b/README.CVS-RULES
index c766837a87..3de9b5e262 100644
--- a/README.CVS-RULES
+++ b/README.CVS-RULES
@@ -89,6 +89,15 @@ The lines above marked with @ will go into NEWS file automagically, and the
 # lines will be omitted from the ChangeLog. Alternatively, you might want
 to modify NEWS file directly and not use the @ lines.
 
+If you fix some bugs, you should note the bug ID numbers in your
+commit message. Bug ID should be prefixed by "#" for easier access to
+bug report when developers are browsing CVS via. LXR or Bonsai.
+
+Example:
+
+Fixed pgsql notice handler double free crash bug. Bug #14016
+@ Fixed pgsql notice handler double free crash bug. Bug #14016
+
 If you don't see your messages in ChangeLog and NEWS right away, don't worry!
 These files are updated once a day, so your stuff will not show up until
 somewhat later. Don't go adding stuff to NEWS by hand if you already put @