summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian2002-11-05 21:53:24 +0000
committerBruce Momjian2002-11-05 21:53:24 +0000
commit6ac7538337e65827e4d48516ca2cd8c6ae6c5c21 (patch)
tree9d5d21dc42a4ecfed5289ac201a5c179cee63cc1
parentd3d54d4b415070fca011889f1aa7d5ec95a6ccb7 (diff)
Update FAQ_DEV.
-rw-r--r--doc/FAQ_DEV11
-rw-r--r--doc/src/FAQ/FAQ_DEV.html12
2 files changed, 11 insertions, 12 deletions
diff --git a/doc/FAQ_DEV b/doc/FAQ_DEV
index fdbea0f273e..a2aae877822 100644
--- a/doc/FAQ_DEV
+++ b/doc/FAQ_DEV
@@ -1,7 +1,7 @@
Developer's Frequently Asked Questions (FAQ) for PostgreSQL
- Last updated: Tue Nov 5 16:49:16 EST 2002
+ Last updated: Tue Nov 5 16:52:46 EST 2002
Current maintainer: Bruce Momjian ([email protected])
@@ -325,7 +325,7 @@
First, we support 15+ operating systems, so any new feature has to be
well established before we will consider it. Second, most new
- wizz-bang features don't provide dramatic improvements. Third, the
+ wizz-bang features don't provide dramatic improvements. Third, they
usually have some downside, such as decreased reliability or
additional code required. Therefore, we don't rush to use new features
but rather wait for the feature to be established, then ask for
@@ -339,10 +339,9 @@
remaining backend startup time.
* The backend code would be more complex.
- So, we are not "asleep at the switch" as they say with regard to new
- features, it is just that we are cautious about their adoption. The
- TODO list often contains links to discussions showing our reasoning in
- these areas.
+ So, we are not ignorant of new features. It is just that we are
+ cautious about their adoption. The TODO list often contains links to
+ discussions showing our reasoning in these areas.
1.10) How are RPM's packaged?
diff --git a/doc/src/FAQ/FAQ_DEV.html b/doc/src/FAQ/FAQ_DEV.html
index 33068df6ca1..6b54fbce936 100644
--- a/doc/src/FAQ/FAQ_DEV.html
+++ b/doc/src/FAQ/FAQ_DEV.html
@@ -12,7 +12,7 @@
<H1>Developer's Frequently Asked Questions (FAQ) for
PostgreSQL</H1>
- <P>Last updated: Tue Nov 5 16:49:16 EST 2002</P>
+ <P>Last updated: Tue Nov 5 16:52:46 EST 2002</P>
<P>Current maintainer: Bruce Momjian (<A href=
@@ -393,7 +393,7 @@
<P>First, we support 15+ operating systems, so any new feature has
to be well established before we will consider it. Second, most new
<I>wizz-bang</I> features don't provide <I>dramatic</I>
- improvements. Third, the usually have some downside, such as
+ improvements. Third, they usually have some downside, such as
decreased reliability or additional code required. Therefore, we
don't rush to use new features but rather wait for the feature to be
established, then ask for testing to show that a measurable
@@ -413,10 +413,10 @@
<LI>The backend code would be more complex.</LI>
</UL>
- <P>So, we are not "asleep at the switch" as they say with regard to
- new features, it is just that we are cautious about their
- adoption. The TODO list often contains links to discussions
- showing our reasoning in these areas.</P>
+ <P>So, we are not ignorant of new features. It is just that
+ we are cautious about their adoption. The TODO list often
+ contains links to discussions showing our reasoning in
+ these areas.</P>
<H3><A name="1.10">1.10</A>) How are RPM's packaged?</H3>