|
12 | 12 | <H1>Developer's Frequently Asked Questions (FAQ) for |
13 | 13 | PostgreSQL</H1> |
14 | 14 |
|
15 | | -<P>Last updated: Tue Nov 2715:45:22 EST 2001</P> |
| 15 | +<P>Last updated: Tue Nov 2716:48:42 EST 2001</P> |
16 | 16 |
|
17 | 17 |
|
18 | 18 | <P>Current maintainer: Bruce Momjian (<Ahref= |
@@ -651,9 +651,10 @@ <H3><A name="16">16</A>) How are CVS branches managed?</H3> |
651 | 651 | next release. |
652 | 652 |
|
653 | 653 | The first thing you have to know is the branch name for the branch you |
654 | | -are interested in getting at. Ian Lance Taylor points out that branches |
655 | | -and tags can be distiguished by using "cvs status -v". Typical branch |
656 | | -names are: |
| 654 | +are interested in getting at. To do this, look at some long-lived file, |
| 655 | +say the top-level HISTORY file, with "cvs status -v" to see what the |
| 656 | +branch names are. (Thanks to Ian Lance Taylor for pointing out that |
| 657 | +this is the easiest way to do it.) Typical branch names are: |
657 | 658 |
|
658 | 659 | REL7_1_STABLE |
659 | 660 | REL7_0_PATCHES |
|