/[guile]/guile/guile-core/ANON-CVS
ViewVC logotype

Diff of /guile/guile-core/ANON-CVS

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.11 by jimb, Tue Oct 5 19:07:39 1999 UTC revision 1.11.4.1 by ttn, Tue Feb 5 20:55:49 2002 UTC
# Line 77  guile-cvs-subscribe-foo=bar.com@egcs.cyg Line 77  guile-cvs-subscribe-foo=bar.com@egcs.cyg
77    
78  Questions ============================================================  Questions ============================================================
79    
 (I don't know if they'll be "frequently asked" or not yet!)  
   
80  - It takes forever to do an update; what can I do to speed it up?  - It takes forever to do an update; what can I do to speed it up?
81    
82    CVS tries to be smart about what it sends; it will transmit and    CVS tries to be smart about what it sends; it will transmit and
# Line 92  Questions ============================== Line 90  Questions ==============================
90    
91    See the CVS documentation for more details.    See the CVS documentation for more details.
92    
   
93  - What happens if I've changed files in my working directory, and then  - What happens if I've changed files in my working directory, and then
94    I do an update?    I do an update?
95    
# Line 109  Questions ============================== Line 106  Questions ==============================
106    shouldn't need to have them installed, if you don't want to change    shouldn't need to have them installed, if you don't want to change
107    those sources.  If you do, see the section in `README' called    those sources.  If you do, see the section in `README' called
108    `Hacking It Yourself'.    `Hacking It Yourself'.
109    
110    - How can I avoid horrible confusion when dealing with branches?
111    
112      Because the auto* tools are version control system agnostic, there is
113      no support for regenerating files based on which branch of the source
114      tree you are "on".  This means that "cvs update -r BRANCH" will
115      probably leave you w/ inconsistent configure, config.status, etc.,
116      which cannot be brought back into sync w/o re-running autogen.sh.
117    
118      So, the best advice is to:
119       (1) dedicate a directory per branch; and
120       (2) always run "./autogen.sh && ./configure ..." after a
121           "cvs update -r BRANCH"
122    
123      If you do (1), you only need to do (2) once, so this is Recommended.

Legend:
Removed from v.1.11  
changed lines
  Added in v.1.11.4.1

savannah-hackers-public@gnu.org
ViewVC Help
Powered by ViewVC 1.1.26