From 882e2899f05891f5397b1bcab1177b85e5f46240 Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Tue, 27 Nov 2001 21:48:45 +0000
Subject: [PATCH] Update FAQ_DEV.
---
doc/src/FAQ/FAQ_DEV.html | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/doc/src/FAQ/FAQ_DEV.html b/doc/src/FAQ/FAQ_DEV.html
index 3c47a4ca291..d1652eedd3b 100644
--- a/doc/src/FAQ/FAQ_DEV.html
+++ b/doc/src/FAQ/FAQ_DEV.html
@@ -12,7 +12,7 @@
<H1>Developer's Frequently Asked Questions (FAQ) for
PostgreSQL</H1>
- <P>Last updated: Tue Nov 27 15:45:22 EST 2001</P>
+ <P>Last updated: Tue Nov 27 16:48:42 EST 2001</P>
<P>Current maintainer: Bruce Momjian (<A href=
@@ -651,9 +651,10 @@ for a stable release just before starting the development cycle for the
next release.
The first thing you have to know is the branch name for the branch you
-are interested in getting at. Ian Lance Taylor points out that branches
-and tags can be distiguished by using "cvs status -v". Typical branch
-names are:
+are interested in getting at. To do this, look at some long-lived file,
+say the top-level HISTORY file, with "cvs status -v" to see what the
+branch names are. (Thanks to Ian Lance Taylor for pointing out that
+this is the easiest way to do it.) Typical branch names are:
REL7_1_STABLE
REL7_0_PATCHES
--
GitLab