|
|
|
|
@ -12,7 +12,7 @@ |
|
|
|
|
<H1>Developer's Frequently Asked Questions (FAQ) for |
|
|
|
|
PostgreSQL</H1> |
|
|
|
|
|
|
|
|
|
<P>Last updated: Mon Jul 19 16:30:05 EDT 2004</P> |
|
|
|
|
<P>Last updated: Mon Oct 4 11:29:26 EDT 2004</P> |
|
|
|
|
|
|
|
|
|
<P>Current maintainer: Bruce Momjian (<A href= |
|
|
|
|
"mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)<BR> |
|
|
|
|
@ -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.</P> |
|
|
|
|
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.</P> |
|
|
|
|
|
|
|
|
|
<P>To update the source tree, there are two ways. You can generate |
|
|
|
|
a patch against your current source tree, perhaps using the |
|
|
|
|
|