Commit 49564ef4 authored by kiko%async.com.br's avatar kiko%async.com.br

Minor adjustment to documentation to account for changes made in bug

229800: whineatnews.pl doesn't whine about REOPENED bugs. Patch written by me and ignored by Gerv :-P
parent 96a0037a
......@@ -578,8 +578,8 @@ perl -pi -e 's@#\!/usr/bin/perl@#\!/usr/local/bin/perl@' *cgi *pl
<qandaentry>
<question id="faq-email-whine">
<para>
I want whineatnews.pl to whine at something different to only new
bugs. How do I do it?
I want whineatnews.pl to whine at something other than new and
reopened bugs. How do I do it?
</para>
</question>
<answer>
......
<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.1.2//EN"> -->
<!-- $Id: installation.xml,v 1.57 2004/01/15 23:54:39 gerv%gerv.net Exp $ -->
<!-- $Id: installation.xml,v 1.58 2004/01/16 00:32:57 kiko%async.com.br Exp $ -->
<chapter id="installation">
<title>Installation</title>
......@@ -1053,7 +1053,7 @@ proc filter_deny { why } {
<para>By now you have a fully functional Bugzilla, but what good are
bugs if they're not annoying? To help make those bugs more annoying you
can set up Bugzilla's automatic whining system to complain at engineers
which leave their bugs in the NEW state without triaging them.
which leave their bugs in the NEW or REOPENED state without triaging them.
</para>
<para>
This can be done by
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment