diff --git a/doc/FAQ_DEV b/doc/FAQ_DEV index 1e2ae78704e..257de830329 100644 --- a/doc/FAQ_DEV +++ b/doc/FAQ_DEV @@ -1,7 +1,7 @@ Developer's Frequently Asked Questions (FAQ) for PostgreSQL - Last updated: Mon Jul 19 16:30:05 EDT 2004 + Last updated: Mon Oct 4 11:29:26 EDT 2004 Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us) @@ -132,9 +132,10 @@ have to download the entire source each time, only the changed files. Anonymous CVS does not allows developers to update the remote source tree, though privileged developers can do this. There is a CVS section - in our documentation that describes how to use remote CVS. You can - also use CVSup, which has similarly functionality, and is available - from ftp.postgresql.org. + (http://developer.postgresql.org/docs/postgres/cvs.html) in our + documentation that describes how to use remote CVS. You can also use + CVSup, which has similarly functionality, and is available from + ftp.postgresql.org. To update the source tree, there are two ways. You can generate a patch against your current source tree, perhaps using the make_diff diff --git a/doc/src/FAQ/FAQ_DEV.html b/doc/src/FAQ/FAQ_DEV.html index 62e1516900d..a2cba71b154 100644 --- a/doc/src/FAQ/FAQ_DEV.html +++ b/doc/src/FAQ/FAQ_DEV.html @@ -12,7 +12,7 @@

Developer's Frequently Asked Questions (FAQ) for PostgreSQL

-

Last updated: Mon Jul 19 16:30:05 EDT 2004

+

Last updated: Mon Oct 4 11:29:26 EDT 2004

Current maintainer: Bruce Momjian (pgman@candle.pha.pa.us)
@@ -175,9 +175,10 @@ don't have to download the entire source each time, only the changed files. Anonymous CVS does not allows developers to update the remote source tree, though privileged developers can do this. - There is a CVS section in our documentation that describes how to - use remote CVS. You can also use CVSup, which has similarly - functionality, and is available from ftp.postgresql.org.

+ There is a CVS section (http://developer.postgresql.org/docs/postgres/cvs.html) + in our documentation that describes how to use remote CVS. You can + also use CVSup, which has similarly functionality, and is available + from ftp.postgresql.org.

To update the source tree, there are two ways. You can generate a patch against your current source tree, perhaps using the