| Title: | USG buildhelp questions/answers |
| Moderator: | SMURF::FILTER |
| Created: | Mon Apr 26 1993 |
| Last Modified: | Mon Jan 20 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2763 |
| Total number of notes: | 5802 |
Date Of Receipt: 22-AUG-1994 08:13:38.04 From: WASTED::grava "Bill Grava USG 22-Aug-1994 0811" To: odehelp@DEC:.zko.wasted CC: grava@DEC:.zko.wasted Subj: argghhh! I did a really stupid thing. I had build a sandbox where i bco'd some files and bcreate'd three new files. But then, I decided to undo the sandbox. I ran bco -u -o -all to undo the files I'd bco'd, but I didn't run bcreate -undo -all to destroy the stuff I'd bcreate'd. When I built the new sandbox and went to bcreate the files (again), I couldn't. This is what happens: <sablelab1:/big1/sandbox/rmtest/src> bcreate kernel/data/rm_data.c [ ./kernel/data/rm_data.c ] [ source control information already exists in file:"./kernel/data/rm_data.c,v" ] There must be some sort of magic incantation to get me out of this mess, but I can't find it. Anybody got any ideas? Thanks, bill
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 910.1 | Re: argghhh! | SMURF::FILTER | Automatic Posting Software - mail to flume::puck | Mon Aug 22 1994 10:52 | 13 |
Date Of Receipt: 22-AUG-1994 08:58:58.49 From: FLUME::jmcg "Jim McGinness" To: grava@DEC:.zko.flume CC: odehelp@DEC:.zko.flume Subj: Re: argghhh! Don't bcreate, just bco. If you had successfully outdated all the revs of the files you had created, the reaper scripts would eventually have gotten rid of the underlying, almost-empty RCS files. That hasn't happened yet, so you can't use bcreate again. -- jmcg | |||||