From 5159ae5142a63c13992b335e33ad347adaa3ac70 Mon Sep 17 00:00:00 2001 From: "jocuri%softhome.net" <> Date: Sun, 2 Nov 2003 22:04:28 +0000 Subject: Rebuilding documentation for the 2.17.5 release; the docbook system on landfill proved to be broken. --- docs/html/hintsandtips.html | 27 +++++++++++++++++++-------- 1 file changed, 19 insertions(+), 8 deletions(-) (limited to 'docs/html/hintsandtips.html') diff --git a/docs/html/hintsandtips.html b/docs/html/hintsandtips.html index c8311f1e5..c3b2ed8e4 100644 --- a/docs/html/hintsandtips.html +++ b/docs/html/hintsandtips.html @@ -4,8 +4,7 @@ >Hints and Tips

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 +148,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 +181,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 +205,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 +231,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.1