summaryrefslogtreecommitdiff
path: root/README.CVS-RULES
diff options
context:
space:
mode:
authorYasuo Ohgaki <yohgaki@php.net>2002-02-28 06:21:09 +0000
committerYasuo Ohgaki <yohgaki@php.net>2002-02-28 06:21:09 +0000
commit1c12a65f826def825413fea38c21f9b2cd00f8e8 (patch)
treebd5e6e297cb700f34d77ab3b0cd926efed278310 /README.CVS-RULES
parent98861da887022a2c0338161e393645748562df8e (diff)
downloadphp-git-1c12a65f826def825413fea38c21f9b2cd00f8e8.tar.gz
Added how to put bug ID in commit message.
Diffstat (limited to 'README.CVS-RULES')
-rw-r--r--README.CVS-RULES9
1 files changed, 9 insertions, 0 deletions
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 @