| Date Of Receipt: 30-AUG-1996 16:42:35.26
From: FLUME::jmf "Joshua M. Friedman Digital UNIX 30-Aug-1996 1641"
To: Carmen Yarrusso USG <yarrusso@DEC:.zko.flume>
CC: odehelp@DEC:.zko.flume, jmf@DEC:.zko.flume
Subj: Re: Viewing source changes right after bsubmit
Carmen, there is a tree we call the "submit pool" which is the name of
the release with no extension. Eg. steelos or v32csupportos. When you
do a submit it goes into this tree; you can cd there and look at the
file. In that tree in logs/bsubmit.log and logs/SNAPSHOT are a record
of your submit.
Each time we do a build we grab new changes in the submit tree, build
them in an internal .bld tree, and then if the build's good copy the
results to a .nightly tree.
The way we have "wired" ode, bco will give you a copy of the file
in the tree you are backed to. If you want to bco the file that's
in the submit tree, and you're currently backed to the .nightly,
do this, for example:
resb v40supportos
bco file
resb v40supportos.nightly
(resb will say to exit and restart workon, but If you're resb'ing
back and forth like you don't need environment variables to
change, so there's no need to do that)
You can check-out unlocked a different version than the default,
eg, while backed to v40supportos.nightly:
bco -u -rV40SUPPORTOS file
-josh
--------
Date: Wed, 28 Aug 1996 10:43:31 -0400
From: Carmen Yarrusso USG <yarrusso>
Message-Id: <9608281443.AA25629@guru.zk3.dec.com>
To: odehelp
Subject: Viewing source changes right after bsubmit
When I do a bsubmit and outdate all revs on a source file,
I understand that the file resides in some interim place
before the pool build happens--then after the build, I
assume the link is restored and I can see my latest changes
by just bcoing the source file. How can I view my changes
after the bsubmit and outdating, but before the actual build?
Carmen Yarrusso
|