From 07ebb9fba9731d9590015e97a9e3f44b2ac8384d Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Fri, 25 Mar 2005 00:51:04 +0000
Subject: [PATCH] Add URL of how to report bugs:

	http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
---
 doc/src/sgml/problems.sgml | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/doc/src/sgml/problems.sgml b/doc/src/sgml/problems.sgml
index 94100815bc..c841165809 100644
--- a/doc/src/sgml/problems.sgml
+++ b/doc/src/sgml/problems.sgml
@@ -1,5 +1,5 @@
 <!--
-$PostgreSQL: pgsql/doc/src/sgml/problems.sgml,v 2.20 2005/01/30 21:31:48 tgl Exp $
+$PostgreSQL: pgsql/doc/src/sgml/problems.sgml,v 2.21 2005/03/25 00:51:04 momjian Exp $
 -->
 
 <sect1 id="bug-reporting">
@@ -265,7 +265,9 @@ $PostgreSQL: pgsql/doc/src/sgml/problems.sgml,v 2.20 2005/01/30 21:31:48 tgl Exp
    Do not be afraid if your bug report becomes rather lengthy. That is a fact of life.
    It is better to report everything the first time than us having to squeeze the
    facts out of you. On the other hand, if your input files are huge, it is
-   fair to ask first whether somebody is interested in looking into it.
+   fair to ask first whether somebody is interested in looking into it.  Here is
+   an <ulink url="http://www.chiark.greenend.org.uk/~sgtatham/bugs.html">
+   article</ulink> that outlines some more tips on reporting bugs.
   </para>
 
   <para>
-- 
2.11.0