Update FAQ_DEV.

diff --git a/doc/src/FAQ/FAQ_DEV.html b/doc/src/FAQ/FAQ_DEV.html
index 0ca9fb0277d2b6235a9f815fee3d3edc1c900807..6b44f1061eb264eef43287c31d935d9616ca13e3 100644 (file)
--- 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 27 19:09:59 EST 2001</P>
+    <P>Last updated: Tue Nov 27 19:32:07 EST 2001</P>
 
     
     <P>Current maintainer: Bruce Momjian (<A href=
@@ -550,6 +550,7 @@
 
     <P>This was written by Lamar Owen:</P>
 <PRE>
+Thu, 03 May 2001 21:22:05 -0400
 As to how the RPMs are built -- to answer that question sanely requires
 me to know how much experience you have with the whole RPM paradigm. 
 'How is the RPM built?' is a multifaceted question.  The obvious simple
@@ -642,6 +643,7 @@ necessary to build RPMs from their Official Tarball (TM).
 
     <P>This was written by Tom Lane:</P>
 <PRE>
+Mon, 07 May 2001 19:35:03 -0400
 If you just do basic "cvs checkout", "cvs update", "cvs commit", then
 you'll always be dealing with the HEAD version of the files in CVS.
 That's what you want for development, but if you need to patch past
@@ -703,6 +705,7 @@ or two, so that we won't have to double-patch the first wave of fixes.
     development?</H3>
     <P>This was written by Lamar Owen:</P>
 <PRE>
+Fri, 22 Jun 2001 12:59:03 -0400
 &gt; If someone was interested in joining the development team, where would
 &gt; they...
 &gt; -  Find a description of the open source development process used by the