aboutsummaryrefslogtreecommitdiff
path: root/doc/src/sgml/problems.sgml
diff options
context:
space:
mode:
Diffstat (limited to 'doc/src/sgml/problems.sgml')
-rw-r--r--doc/src/sgml/problems.sgml8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/src/sgml/problems.sgml b/doc/src/sgml/problems.sgml
index e324f912f14..cd4f65bb153 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.23 2005/03/31 03:54:38 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/problems.sgml,v 2.24 2005/04/09 03:52:43 momjian Exp $
-->
<sect1 id="bug-reporting">
@@ -266,7 +266,7 @@ $PostgreSQL: pgsql/doc/src/sgml/problems.sgml,v 2.23 2005/03/31 03:54:38 momjian
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. Here is
- an article, <ulink url="http://www.chiark.greenend.org.uk/~sgtatham/bugs.html"></ulink>,
+ an <ulink url="http://www.chiark.greenend.org.uk/~sgtatham/bugs.html">article</ulink>
that outlines some more tips on reporting bugs.
</para>
@@ -305,8 +305,8 @@ $PostgreSQL: pgsql/doc/src/sgml/problems.sgml,v 2.23 2005/03/31 03:54:38 momjian
<para>
Another method is to fill in the bug report web-form available
- at the project's web site,
- <ulink url="http://www.postgresql.org/"></ulink>.
+ at the project's
+ <ulink url="http://www.postgresql.org/">web site</ulink>.
Entering a bug report this way causes it to be mailed to the
<email>pgsql-bugs@postgresql.org</email> mailing list.
</para>