From 11f88ccab7c566d7f4d709edb387ee4bc7d52aa7 Mon Sep 17 00:00:00 2001 From: simonmar Date: Wed, 28 May 2003 09:05:21 +0000 Subject: [PATCH] [project @ 2003-05-28 09:05:21 by simonmar] Don't recommend that people do 'cvs update -d' at the top level of an fptools tree. --- docs/building/building.sgml | 18 +++++++++++++----- 1 file changed, 13 insertions(+), 5 deletions(-) diff --git a/docs/building/building.sgml b/docs/building/building.sgml index 27ba81e..bcf3cf4 100644 --- a/docs/building/building.sgml +++ b/docs/building/building.sgml @@ -578,13 +578,21 @@ $ cvs commit -F commit-message directory $ cd fptools -$ cvs update -Pd 2>&1 | tee log +$ cvs update -P 2>&1 | tee log Look at the log file, and fix any conflicts (denoted by a - C in the first column). If you're using multiple - build trees, then for every build tree you have pointing at this - source tree, you need to update the links in case any new files - have appeared: + C in the first column). New directories may have + appeared in the repository; CVS doesn't check these out by + default, so to get new directories you have to explicitly do + +$ cvs update -d + in each project subdirectory. Don't do this at the top level, + because then all the projects will be + checked out. + + If you're using multiple build trees, then for every build + tree you have pointing at this source tree, you need to update + the links in case any new files have appeared: $ cd build-tree -- 1.7.10.4