| Date Of Receipt: 7-MAR-1995 12:42:43.42
From: SMURF::ALPHA::"[email protected]" "07-Mar-1995 1238"
To: [email protected]
CC: [email protected]
Subj: Re: BCO and ID strings
When you bco a file, it does indeed create a private branch for your work
x.x.x.1. The content of the file will be whatever the "check_out_config" is
set to for that tree. The ID string will reflect that version because at that
point, your private branch really has no content. If you do a blog -r file
though at this point, you'll see the marker for your private branch with a
label saying
"*** Initial Branch Revision ***"
When you bci, the file goes onto your private branch and the ID string is
modified to reflect your private branch. If you bco again, you'll see that the
ID string has changed again to show this and is now x.x.x.2.
When you bsubmit the file, it needs to become part of the public branch for
that stream n.n.n and your private branch needs to go away or become outdated
in ODE lingo. Doing this will prevent version/merge skew when you work on this
file in the future. So as the file is submitted, its ID string changes onece
more to become the highest number on the public branch. If you then bco,
that's the version you'll get (assuming you're backed by the submit tree not
nightly).
-Grant
| I am a little confused. When I BCO a file I would expect the ID string
| to be changed in some way to indicate the fact that the file I am building
| is a branch version but this does not appear to be the case. The ID does
| not appear to change until I do a BCI. Is there some option I can use
| to force this behavior? Do I need to manually edit the ID string? If
| I do this, what happend when I BCI. This appears broken to me.
|
| Mike Schloss
|