From 7407cb3069182253ff4218450237bec5726f21d2 Mon Sep 17 00:00:00 2001 From: "jake%bugzilla.org" <> Date: Thu, 6 Feb 2003 10:45:24 +0000 Subject: This checkin contains two fixes: * Bug 191971 - The guide incorrectly stated that you could resolve a bug via email * Provide an example of a glossary term in the document conventions section --- docs/txt/Bugzilla-Guide.txt | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) (limited to 'docs/txt') 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 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. -- cgit v1.2.3-24-g4f1b