From 1b2aa767929784a37212b9e3dc01f9e119c4a9d6 Mon Sep 17 00:00:00 2001 From: "gerv%gerv.net" <> Date: Sun, 22 Dec 2002 00:33:39 +0000 Subject: Rebuild HTML and text versions of documentation for 2.17.2 release. --- docs/html/hintsandtips.html | 24 ++++++++++++++++++------ 1 file changed, 18 insertions(+), 6 deletions(-) (limited to 'docs/html/hintsandtips.html') diff --git a/docs/html/hintsandtips.html b/docs/html/hintsandtips.html index c20131bd4..8638a3167 100644 --- a/docs/html/hintsandtips.html +++ b/docs/html/hintsandtips.html @@ -73,7 +73,9 @@ CLASS="section" >

3.2. Hints and Tips

3.2. Hints and Tips

This section distills some Bugzilla tips and best practices that have been developed.

3.2.1. Autolinkification

3.2.1. Autolinkification

Bugzilla comments are plain text - so posting HTML will result in literal HTML tags rather than being interpreted by a browser. @@ -145,7 +149,9 @@ CLASS="section" >

3.2.2. Quicksearch

3.2.2. Quicksearch

Quicksearch is a single-text-box query tool which uses metacharacters to indicate what is to be searched. For example, typing @@ -176,7 +182,9 @@ CLASS="section" >

3.2.3. Comments

3.2.3. Comments

If you are changing the fields on a bug, only comment if either you have something pertinent to say, or Bugzilla requires it. @@ -198,7 +206,9 @@ CLASS="section" >

3.2.4. Attachments

3.2.4. Attachments

Use attachments, rather than comments, for large chunks of ASCII data, such as trace, debugging output files, or log files. That way, it doesn't @@ -222,7 +232,9 @@ CLASS="section" >

3.2.5. Filing Bugs

3.2.5. Filing Bugs

Try to make sure that everything said in the summary is also said in the first comment. Summaries are often updated and this will -- cgit v1.2.3-24-g4f1b