From 179211a68308d051d6ae70046b4cd5ec635e1bc7 Mon Sep 17 00:00:00 2001
From: Bruce Momjian
Date: Tue, 22 Nov 2005 15:21:54 +0000
Subject: [PATCH] Markup TODO as a URL.
---
doc/FAQ | 11 +++++------
doc/src/FAQ/FAQ.html | 23 ++++++++++++++---------
2 files changed, 19 insertions(+), 15 deletions(-)
diff --git a/doc/FAQ b/doc/FAQ
index 79b12c187f..faf7a59c93 100644
--- a/doc/FAQ
+++ b/doc/FAQ
@@ -1,7 +1,7 @@
Frequently Asked Questions (FAQ) for PostgreSQL
- Last updated: Tue Nov 22 10:16:48 EST 2005
+ Last updated: Tue Nov 22 10:21:51 EST 2005
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
@@ -194,15 +194,14 @@
1.8) How do I submit a bug report?
Visit the PostgreSQL bug form at
- http://www.postgresql.org/support/submitbug.
-
- Also check out our ftp site ftp://ftp.PostgreSQL.org/pub/ to see if
- there is a more recent PostgreSQL version.
+ http://www.postgresql.org/support/submitbug. Also check out our ftp
+ site ftp://ftp.PostgreSQL.org/pub/ to see if there is a more recent
+ PostgreSQL version.
Bugs submitted using the bug form or posted to any PostgreSQL mailing
list typically generates one of the following replies:
* It is not a bug, and why
- * It is a known bug and is known already on the TODO list
+ * It is a known bug and is already on the TODO list
* The bug has been fixed in the current release
* The bug has been fixed but is not packaged yet in an official
release
diff --git a/doc/src/FAQ/FAQ.html b/doc/src/FAQ/FAQ.html
index dc98fb783d..634286dc82 100644
--- a/doc/src/FAQ/FAQ.html
+++ b/doc/src/FAQ/FAQ.html
@@ -10,7 +10,7 @@
alink="#0000ff">
Frequently Asked Questions (FAQ) for PostgreSQL
- Last updated: Tue Nov 22 10:16:48 EST 2005
+ Last updated: Tue Nov 22 10:21:51 EST 2005
Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
@@ -247,9 +247,8 @@
Visit the PostgreSQL bug form at
- http://www.postgresql.org/support/submitbug.
-
- Also check out our ftp site .
+ Also check out our ftp site ftp://ftp.PostgreSQL.org/pub/ to
see if there is a more recent PostgreSQL version.
@@ -257,7 +256,8 @@
list typically generates one of the following replies:
- It is not a bug, and why
- - It is a known bug and is known already on the TODO list
+ - It is a known bug and is already on the
+ TODO list
- The bug has been fixed in the current release
- The bug has been fixed but is not packaged yet in an official
release
@@ -275,7 +275,8 @@
- A patch has been created and will be included in the next major
or minor release
- The bug cannot be fixed immediately and is added
- to the TODO list
+ to the TODO
+ list
@@ -290,7 +291,9 @@
A feature request usually results in one of the following
replies:
- - The feature is already on the TODO list
+ - The feature is already on the
+ TODO
+ list
- The feature is not desired because:
- It duplicates existing functionality that already
@@ -300,11 +303,13 @@
- The feature would be insecure or unreliable
- - The new feature is added to the TODO list
+ - The new feature is added to the
+ TODO list
PostgreSQL does not use a bug tracking system because we find
- it more efficient to respond directly to email and keep the TODO
+ it more efficient to respond directly to email and keep the
+ TODO
list up-to-date. In practice, bugs don't last very long in the
software, and bugs that affect a large number of users are fixed
rapidly. The only single place to find all changes, improvements,