| Date Of Receipt: 21-DEC-1995 15:14:46.17
From: SMURF::ALPHA::"vandyck@cardinal.zk3.dec.com" "21-Dec-1995 1512"
To: "Lori Ransegnola (908) 577-6051, DTN 462-6051" <ljr@unx.dec.com>
CC: odehelp@zk3.dec.com
Subj: Re: Problem noticed with duplicate set names in different sandboxes
| In a BL6 sandbox, under a set name 'fix_25057', I made some changes to
| the file usr/bin/llogin/llogin.c. Today, in a BL9 sandbox, coincidentally,
| under a set name 'fix_25057', I checked out the file usr/bin/llogin/llogin.c
and
| found that it contained the changes that had been made, and never submitted,
in
| the BL6 sandbox.
|
| I ended up saveing the file in the BL6 sandbox, 'bcs -o -u'ing the file
| in the BL6 sandbox, and then was able to check out the usr/bin/llogin/llogin.
c
| in my BL9 sandbox without those changes present.
|
| It doesn't sound to me like this is the way things are supposed to work
.
| Is this because the set names were the same??
You got it. That's exactly the way it's supposed to work. You get the file
that goes with your setname.
-Grant
|
| Date Of Receipt: 21-DEC-1995 15:49:53.75
From: SMURF::ALPHA::jmf "Joshua M. Friedman OSF/UNIX SDE"
To: ljr@unx.dec.com
CC: odehelp@DEC:.zko.alpha
Subj: Re: Problem noticed with duplicate set names in different sandboxes
Lori,
> Is this because the set names were the same??
Yes; you may not use the same set name in more than one sandbox on the
same files; the setname (with your principal name but not sandbox name
prepended) is the symbol RCS uses internally to identify your private
revs (branch). There's an outstanding bug report on this (ODE should
block the 2nd bco of a file already bco'd in the first sandbox, but I
doesn't yet.)
The only problem is that, depending on the order of events, the bco in
the 2nd sandbox will not have the needed src/.BCSconfig file entry (which
is what bsubmit uses to determine if a merge needs to be done.)
If you bco -u -o'd the file from BOTH sandboxes and started fresh in
the second one, then you're ok. This is the best way to be sure you're
all set.
-josh
------
To: odehelp@zk3.dec.com
Cc: ljr@unx.dec.com
Subject: Problem noticed with duplicate set names in different sandboxes
Date: Thu, 21 Dec 95 13:52:54 -0500
From: "Lori Ransegnola (908) 577-6051, DTN 462-6051" <ljr@unx.dec.com>
Hi,
In a BL6 sandbox, under a set name 'fix_25057', I made some changes to
the file usr/bin/llogin/llogin.c. Today, in a BL9 sandbox, coincidentally,
under a set name 'fix_25057', I checked out the file usr/bin/llogin/llogin.c and
found that it contained the changes that had been made, and never submitted, in
the BL6 sandbox.
I ended up saveing the file in the BL6 sandbox, 'bcs -o -u'ing the file
in the BL6 sandbox, and then was able to check out the usr/bin/llogin/llogin.c
in my BL9 sandbox without those changes present.
It doesn't sound to me like this is the way things are supposed to work.
Is this because the set names were the same??
Lori Ransegnola
|