| Date Of Receipt: 8-NOV-1994 13:02:38.34
From: FLAMBE::"[email protected]" "Grant Van Dyck 08-Nov-1994 1259"
To: [email protected]
CC: [email protected]
Subj: Re: OSF1 ODE BUILD QUESTION
| I have a sandbox backed by GOLDMINX.BL3. I BCO a file
| and make changes. When I BUILD, I get GOLDMINX.BL3 plus
| my changes. When I BCI, I assume that I still get BL3
| plus my changes. When I BSUBMIT, I lose the file as
| well as the changes. Is there some way of being backed
| by a stable area, yet still getting my checked-in changes?
|
| Mike Schloss
|
What do you mean by lose your changes when you bsubmit? The file
goes into the submit tree and out of your sandbox?
If you'd like to reatain the submitted copy in your sandbox, there are
two options:
- use the -noauto_out flag on bsubmit. This will not only leave the
copy in your sandbox, but also your private branch in RCS. The danger
here is that by not outdating your private branch (removing it from RCS)
you may run into merge/bsubmit problems if you work on the same file
at a later time.
- submit the file, then recheck it out unlocked
bco -u -r$NEW filename
-Grant
|
| Date Of Receipt: 8-NOV-1994 13:19:58.41
From: FLUME::jmcg "Jim McGinness"
To: schloss@DEC:.zko.flume
CC: buildhelp odehelp
Subj: Re: OSF1 ODE BUILD QUESTION
I just wanted to amplify on Grant's message...
The circumstances under which -noauto_out is the appropriate thing
is fairly rare: it's sometimes the best way to do dual submits.
For the more usual situation, where you're continuing to do work
on the file after the submit or you're continuing to do work in
the sandbox and want the prior changes to be effective, the bco -u
solution is better. I even think it would be a good idea if a -u
flag were added to bci and bsubmit that would have this effect by
analogy with the -l flag to bci.
-- jmcg
> From vandyck Tue Nov 8 13:00:29 1994
> To: schloss
> Subject: Re: OSF1 ODE BUILD QUESTION
> Date: Tue, 08 Nov 94 12:59:50 -0500
> From: Grant Van Dyck <vandyck>
>
>
> | I have a sandbox backed by GOLDMINX.BL3. I BCO a file
> | and make changes. When I BUILD, I get GOLDMINX.BL3 plus
> | my changes. When I BCI, I assume that I still get BL3
> | plus my changes. When I BSUBMIT, I lose the file as
> | well as the changes. Is there some way of being backed
> | by a stable area, yet still getting my checked-in changes?
> |
> | Mike Schloss
> |
>
> What do you mean by lose your changes when you bsubmit? The file
> goes into the submit tree and out of your sandbox?
>
> If you'd like to reatain the submitted copy in your sandbox, there are
> two options:
>
> - use the -noauto_out flag on bsubmit. This will not only leave the
> copy in your sandbox, but also your private branch in RCS. The danger
> here is that by not outdating your private branch (removing it from RCS)
> you may run into merge/bsubmit problems if you work on the same file
> at a later time.
>
> - submit the file, then recheck it out unlocked
>
> bco -u -r$NEW filename
>
>
> -Grant
>
|