|
12 | 12 | <H1>Developer's Frequently Asked Questions (FAQ) for
|
13 | 13 | PostgreSQL</H1>
|
14 | 14 |
|
15 |
| -<P>Last updated: MonJul 19 16:30:05 EDT 2004</P> |
| 15 | +<P>Last updated: MonOct 4 11:29:26 EDT 2004</P> |
16 | 16 |
|
17 | 17 | <P>Current maintainer: Bruce Momjian (<Ahref=
|
18 | 18 | "mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</A>)<BR>
|
@@ -175,9 +175,10 @@ <H3><A name="1.3">1.3</A>) How do I download/update the current source
|
175 | 175 | don't have to download the entire source each time, only the
|
176 | 176 | changed files. Anonymous CVS does not allows developers to update
|
177 | 177 | the remote source tree, though privileged developers can do this.
|
178 |
| - There is a CVS section in our documentation that describes how to |
179 |
| - use remote CVS. You can also use CVSup, which has similarly |
180 |
| - functionality, and is available from ftp.postgresql.org.</P> |
| 178 | + There is a CVS section (http://developer.postgresql.org/docs/postgres/cvs.html) |
| 179 | + in our documentation that describes how to use remote CVS. You can |
| 180 | + also use CVSup, which has similarly functionality, and is available |
| 181 | + from ftp.postgresql.org.</P> |
181 | 182 |
|
182 | 183 | <P>To update the source tree, there are two ways. You can generate
|
183 | 184 | a patch against your current source tree, perhaps using the
|
|