summaryrefslogtreecommitdiffstats
path: root/docs/txt/Bugzilla-Guide.txt
diff options
context:
space:
mode:
Diffstat (limited to 'docs/txt/Bugzilla-Guide.txt')
-rw-r--r--docs/txt/Bugzilla-Guide.txt7
1 files changed, 4 insertions, 3 deletions
diff --git a/docs/txt/Bugzilla-Guide.txt b/docs/txt/Bugzilla-Guide.txt
index 02f37f79f..ce90ed22f 100644
--- a/docs/txt/Bugzilla-Guide.txt
+++ b/docs/txt/Bugzilla-Guide.txt
@@ -258,6 +258,7 @@ Chapter 1. About This Guide
Prompt of user command under tcsh shell tcsh$
Environment Variables VARIABLE
Emphasized word word
+ Term found in the glossary Bugzilla
Code Example
<para>
Beginning and end of paragraph
@@ -2648,9 +2649,9 @@ patching file globals.pl
Follow the instructions in this Guide for enabling Bugzilla e-mail
integration. Ensure that your check-in script sends an email to your
Bugzilla e-mail gateway with the subject of "[Bug XXXX]", and you can
- have CVS check-in comments append to your Bugzilla bug. If you have
- your check-in script include an @resolution field, you can even change
- the Bugzilla bug state.
+ have CVS check-in comments append to your Bugzilla bug. If you want to
+ have the bug be closed automatically, you'll have to modify the
+ contrib/bugzilla_email_append.pl script.
There is also a CVSZilla project, based upon somewhat dated Bugzilla
code, to integrate CVS and Bugzilla through CVS' ability to email.