(Questions): Add q/a on cvs branch sanity.

ANON-CVS

@@ -77,8 +77,6 @@ guile-cvs-subscribe-foo=bar.com@egcs.cygnus.com.
 
 Questions ============================================================
 
-(I don't know if they'll be "frequently asked" or not yet!)
-
 - It takes forever to do an update; what can I do to speed it up?
 
   CVS tries to be smart about what it sends; it will transmit and
@@ -92,7 +90,6 @@ Questions ============================================================
 
   See the CVS documentation for more details.
 
-
 - What happens if I've changed files in my working directory, and then
   I do an update?
 
@@ -109,3 +106,18 @@ Questions ============================================================
   shouldn't need to have them installed, if you don't want to change
   those sources.  If you do, see the section in `README' called
   `Hacking It Yourself'.
+
+- How can I avoid horrible confusion when dealing with branches?
+
+  Because the auto* tools are version control system agnostic, there is
+  no support for regenerating files based on which branch of the source
+  tree you are "on".  This means that "cvs update -r BRANCH" will
+  probably leave you w/ inconsistent configure, config.status, etc.,
+  which cannot be brought back into sync w/o re-running autogen.sh.
+
+  So, the best advice is to:
+   (1) dedicate a directory per branch; and
+   (2) always run "./autogen.sh && ./configure ..." after a
+       "cvs update -r BRANCH"
+
+  If you do (1), you only need to do (2) once, so this is Recommended.