diff options
author | Bruce Momjian <bruce@momjian.us> | 1998-06-16 03:55:15 +0000 |
---|---|---|
committer | Bruce Momjian <bruce@momjian.us> | 1998-06-16 03:55:15 +0000 |
commit | 5815523b0e9731da9355dfcc6899829a21314855 (patch) | |
tree | 10b796de01af0f4e0dfea689d7fd5d98c6f2e89b /doc/FAQ_DEV | |
parent | b4672e29df8ded8cc5bc1a40320fa8307f525c3b (diff) | |
download | postgresql-5815523b0e9731da9355dfcc6899829a21314855.tar.gz postgresql-5815523b0e9731da9355dfcc6899829a21314855.zip |
Add FAQ_CVS.
Diffstat (limited to 'doc/FAQ_DEV')
-rw-r--r-- | doc/FAQ_DEV | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/doc/FAQ_DEV b/doc/FAQ_DEV index e9f663f5113..a8d8eee0d41 100644 --- a/doc/FAQ_DEV +++ b/doc/FAQ_DEV @@ -113,12 +113,15 @@ existing code doing similar things is helpful. There are several ways to obtain the source tree. Occasional developers can just get the most recent source tree snapshot from ftp.postgresql.org. For -regular developers, you can get CVSup, which is available from +regular developers, you can use CVSup, which is available from ftp.postgresql.org too. CVSup allows you to download the source tree, then occasionally update your copy of the source tree with any new changes. Using CVSup, you don't have to download the entire source each time, only the changed files. CVSup does not allow developers to update the source tree. +Anonymous CVS is available too. See the doc/FAQ_CVS file for more +information. + To update the source tree, there are two ways. You can generate a patch against your current source tree, perhaps using the make_diff tools mentioned above, and send them to the patches list. They will be reviewed, |