| Date Of Receipt: 19-NOV-1993 10:06:30.70
From: WASTED::jmf "Joshua M. Friedman ULTRIX SDE 16-Nov-1993 1713"
To: grava@wasted:zko.dec
CC: odehelp@wasted:zko.dec
Subj: re: cleaning up after a spill....
Bill, what you have marked with <===??????? is, in fact, your working
branch; this is where your work to be submitted is contained, if you
have done a check-in. If you have not yet done a check-in, it is still
your private working branch, where the bci's will "go". The file which
you show below has already had [some or all of] your work checked in by
virtue of the fact that it's not "locked" by you.
If your work has all been bci'd and just has to be bsubmitted, you just
need to recreate the sandbox datafile files; i.e. the two things which
have been wiped out that you are probably unaware of are the following
two files:
in you sandbox/src directory:
.BCSset-William_Grava_keyboard
contains the list of files in your "set" (that you bco'd)
each line is of the form:
./motif/clients/session/keymap/uk_lk201re.decw_keymap
./...
.BCSconfig
contains the list of files in your "set" along with the
"common ancestor" revision - i.e. the version of the file
which was the starting point for your work.
if you are totally up-to-date with the submit tree (i.e.
no new submits have been done on any of the files since
you've started your work), you can re-create this file
using:
bstat -r$NEW -R -V -all > .BCSconfig
(it has the form, eg:
./motif/clients/session/keymap/uk_lk201re.decw_keymap,v <tab> 1.1.4.2
If you really want, you can "undo" all your work by doing
bcs -u -all (if any files are locked)
bcs -o -all (to outdate the branches)
and then start over with bco's.
hope this helps... -josh
------- Forwarded Message
Return-Path: grava
Delivery-Date: Tue, 16 Nov 93 12:40:33 -0500
Return-Path: grava
Received: from wasted.zk3.dec.com by flambe.zk3.dec.com; (5.65/1.1.8.2/01Nov93-1038AM)
id AA10550; Tue, 16 Nov 1993 12:40:30 -0500
Received: by wasted.zk3.dec.com; id AA26939; Tue, 16 Nov 1993 12:39:54 -0500
Message-Id: <[email protected]>
To: odehelp
Subject: cleaning up after a spill....
Date: Tue, 16 Nov 93 12:39:54 -0500
From: ""No wanna work. Wanna bang on keyboard."" <grava>
X-Mts: smtp
I have a problem. While updating my workstation software, I inadvertently
destroyed two sandboxes (with pending submits) on one of the disk drives.
Both are quite easy to recreate -- easy, that is, once I get past the
ODE locks and controls.
What I've done to date is 'bcs -u{n.n.n.n} to release the locks on the
files that I had, and that seems to be OK. Now, when I do 'blog {filename}'
I get something like:
RCS file: ./motif/clients/session/keymap/uk_lk201re.decw_keymap,v
Working file: uk_lk201re.decw_keymap
head: 1.1
branch:
locks: strict
access list:
symbolic names:
GOLDX_PRE_BL7: 1.1.4.2
GOLDX_BL7: 1.1.4.2
AGXHW_BL7: 1.1.4.2
AGXMINOR_BL7: 1.1.4.2
???==> William_Grava_keyboard: 1.1.5 <===???????
AGXMINOR_PRE_BL7: 1.1.4.2
AGXHW_BL6: 1.1.4.2
GOLDX_BL6: 1.1.4.2
AGXMINOR_BL6: 1.1.4.2
AGXHW_BL5: 1.1.4.2
GOLDX_KITBLD: 1.1.4.2
AGXMINOR_PRE_BL6: 1.1.4.2
...
I have two questions--
1. Do I need to get rid of the control file entry marked by the
????????.
2. If I do, how do I do it?
thanks,
- --bill
------- End of Forwarded Message
|