| Date Of Receipt: 3-MAY-1996 00:48:26.00
From: ALPHA::"[email protected]" "Joshua M. Friedman OSF/UNIX SDE"
To: jenny@locus_ode.wdec.locus.com, [email protected]
CC:
Subj: Re: The same set name for different pools
Please check your sandbox src dir for .BCSset-* files and see if
ODE saves your work on the RCS branch named for your set. You cannot
use the same set in more than one sandbox for the same file (as you've
found), though ODE doesn't currently block you (this has been bug-reported).
Yes, do a new bco/bci for the file in the other pools. You can do
a "bco -jV32SUPPORTOS file" while backed to v32c and I believe you'll
get exactly the version from the v32support pool; if this same exact
version belongs in the other pools you can then bci/bsubmit.
-josh
From jenny@locus_ode.wdec.locus.com Mon Apr 29 14:58:43 1996
Delivery-Date: Mon, 29 Apr 96 14:59:01 -0400
Return-Path: jenny@locus_ode.wdec.locus.com
Received: from ralpha.zk3.dec.com by flume.zk3.dec.com; (5.65v3.2/1.1.8.2/16Jan95-0946AM)
id AA03405; Mon, 29 Apr 1996 14:58:43 -0400
Received: from hunch.zk3.dec.com by falpha.zk3.dec.com; (5.65v3.2/1.1.8.2/20May95-1022AM)
id AA25259; Mon, 29 Apr 1996 14:58:38 -0400
Received: from locus_ode.wdec.locus.com by hunch.zk3.dec.com; (5.65v3.2/1.1.8.2/11Mar96-0342PM)
id AA19306; Mon, 29 Apr 1996 14:58:09 -0400
Received: by locus_ode.wdec.locus.com; id AA03472; Mon, 29 Apr 1996 14:59:05 -0400
Message-Id: <9604291859.AA03472@locus_ode.wdec.locus.com>
To: [email protected]
Cc: jenny@locus_ode.wdec.locus.com
Subject: The same set name for different pools
Date: Mon, 29 Apr 96 14:59:04 -0400
From: "Jennifer D. Vu" <jenny@locus_ode.wdec.locus.com>
X-Mts: smtp
Status: R
Hi,
I did a bci/bco the same module in different pools, v32 and v32c,
using the same set name as mgo101106, and it seems like after I
did a bsubmit the fix into v32 pool, I cannot do a bsubmit of
the fix into v32c pool.
falpha.zk3.dec.com <Xm> [32] % bstat TextF.c
[ ./motif/lib/Xm/TextF.c ]
[ There is no branch revison for set Jenny_Vu_mgo101106. ]
What should I do now? Should I bco/bci TextF.c again from/to v32c pool,
and redo a bsubmit for v32c?
The two original copies of TextF.c from v32 and v32c are identical.
I've enclosed my srequests and bsubmits
scripts to v32 and v32c pools below.
Thanks for your help,
Jenny
================================================================================
v32 pool:
--------
falpha.zk3.dec.com <Xm> [49] % mv TextF.c mgo101106_TextF.c
falpha.zk3.dec.com <Xm> [50] % pwd
/share/alpha/usr/staff2/jennyd/sb/v32/src/motif/lib/Xm
falpha.zk3.dec.com <Xm> [51] % bco TextF.c
[ ./motif/lib/Xm/TextF.c ]
[ ./motif/lib/Xm/TextF.c Rev 1.1.29.1 checked out locked ]
falpha.zk3.dec.com <Xm> [52] % diff TextF.c.orig TextF.c
falpha.zk3.dec.com <Xm> [53] % diff TextF.c mgo101106_TextF.c
5096a5097,5105
> #ifdef DEC_MOTIF_BUG_FIX
> /* DEC_MOTIF_BUG_FIX
> * Part 1 of 1
> * Reference: mgo101106
> * Developer: Sam Menaker
> * Description: nextPos should remain the same
> */
> TextFieldScanCompositeBreak( tf, nextPos, XmTEXT_FORWARD,
> #else
5097a5107
> #endif /* DEC_MOTIF_BUG_FIX */
falpha.zk3.dec.com <Xm> [54] %
falpha.zk3.dec.com <Xm> [56] % cp mgo101106_TextF.c TextF.c
falpha.zk3.dec.com <Xm> [57] % bci TextF.c
[ ./motif/lib/Xm/TextF.c ]
[ scanning for HISTORY messages ]
[ found <<<replace with log message ...>>> marker ]
Command? (type "help" for a list) [log]
03-Feb-1995
Fixed CFS.23345 (CLD MGO101106) and CFS.39769 (CLD GOZ100507)
by Sam Menaker. Incorrect deletion of characters in overstrike
mode in XmTextField widgets.
Command? (type "help" for a list) [check-in]
[ ./motif/lib/Xm/TextF.c Rev 1.1.29.1 checked in ]
alpha.zk3.dec.com <Xm> [61] % srequest
This submit request will be logged against release 'v32support'
Is this correct ? [y]:
Enter the baselevel NUMBER [4]:
Is '[email protected]' your correct mailing address ? [y]:
Enter mail alias - must refer to one review committee:
ase_submit build_submit cde_submit
cluster_submit cmds_submit de_submit
etype_submit filesystem_submit habitat_submit
hardware_submit i18n_submit install_submit
kernel_submit ktools_submit lat_submit
mail_submit network_submit ootb_submit
print_submit proc_submit rt_submit
security_submit standards_submit svid_submit
sysman_submit threads_submit vm_submit
workstation_submit xdesktop_submit
[NO_DEFAULT]: workstation_submit
Enter aliases or usernames, in a comma separated list, to add to the
following cc mailing list for this submit request:
[email protected],osf_submit,[email protected]
(enter a blank line to end) :
Press the return key to edit the list of files for this submit request:
./motif/lib/Xm/TextF.c
A bdiff log will be generated from the previous edited list of files.
You can include[i] the bdiff results in this form, specify the location[l]
of a file that contains previously generated bdiff's, or supply a pointer[p]
to place the newly generated bdiff's.
How do you want the bdiff's represented [i|l|p] : i
bstat'ing ./motif/lib/Xm/TextF.c
bdiff'ing ./motif/lib/Xm/TextF.c
********** last Friday I updated my srequest *************************
Fri Apr 26 12:01:08 EDT 1996
falpha.zk3.dec.com <DXm> [69] % workon -sb v32 mgo101106
cd'ing to sandbox source directory: /home/jennyd/sb/v32/src.
starting new shell: /bin/csh.
falpha.zk3.dec.com <src> [31] % cd motif/lib/Xm
falpha.zk3.dec.com <Xm> [32] % srequest -update v32supportx-16-jennyd
This submit request update will be logged against release 'v32support'
Is this correct ? [y]:
Enter the baselevel NUMBER [4]:
Update this form [y|n] ?: y
Submit request 'v32supportx-16-jennyd' has been updated
********** I did a bsubmit TextF.c into v32 pool this morning, 4/29 *******
falpha.zk3.dec.com <DXm> [83] % workon -sb v32 mgo101106
cd'ing to sandbox source directory: /home/jennyd/sb/v32/src.
starting new shell: /bin/csh.
falpha.zk3.dec.com <src> [31] % cd motif/lib/Xm
falpha.zk3.dec.com <Xm> [32] % bstat TextF.c
[ ./motif/lib/Xm/TextF.c ]
version 1.1.29.3 selected
falpha.zk3.dec.com <Xm> [33] % bsubmit -info -auto_out TextF.c
Enter the defect number this submission applies to: v32supportx-16-jennyd
Would lock the hold file.
Would append files to be submitted to hold file.
*** No user interaction would be required during the merge step. ***
Would lock latest version of submitted files.
Would check files in.
Would update default build.
Would generate user log without user interaction.
Would outdate user's versions of files.
Submission -info completed successfully.
falpha.zk3.dec.com <Xm> [34] % bsubmit -auto_out -defect v32supportx-16-jennyd TextF.c
*** No user interaction will be required during the merge step. ***
[ ./motif/lib/Xm/TextF.c checked in onto branch 1.1.30 ]
[ ./motif/lib/Xm/TextF.c Rev 1.1.30.2 checked out ]
[ ./motif/lib/Xm/TextF.c outdated revisions in set Jenny_Vu_mgo101106 ]
Submission completed successfully.
falpha.zk3.dec.com <Xm> [35] %
================================================================================
v32c pool:
---------
falpha.zk3.dec.com <Xm> [51] % workon -sb v32c mgo101106
cd'ing to sandbox source directory: /home/jennyd/sb/v32c/src.
creating new set: Jenny_Vu_mgo101106, setdir: .
starting new shell: /bin/csh.
falpha.zk3.dec.com <src> [31] % cd motif/lib/Xm
falpha.zk3.dec.com <Xm> [34] % mv TextF.c mgo101106_TextF.c
falpha.zk3.dec.com <Xm> [35] % bco TextF.c
[ ./motif/lib/Xm/TextF.c ]
[ ./motif/lib/Xm/TextF.c Rev 1.1.29.2 checked out locked ]
falpha.zk3.dec.com <Xm> [36] % cp mgo101106_TextF.c TextF.c
falpha.zk3.dec.com <Xm> [37] % rm TextF.o
falpha.zk3.dec.com <Xm> [38] % make TextF.o
...
falpha.zk3.dec.com <Xm> [39] % bci TextF.c
[ ./motif/lib/Xm/TextF.c ]
[ scanning for HISTORY messages ]
[ found <<<replace with log message ...>>> marker ]
Command? (type "help" for a list) [log]
03-Apr-1996
Fixed CFS.23345 (CLD MGO101106) and CFS.39769 (CLD GOZ100507)
by Sam Menaker. Incorrect deletion of characters in overstrike
mode in XmTextField widgets.
Command? (type "help" for a list) [check-in]
[ ./motif/lib/Xm/TextF.c Rev 1.1.29.2 checked in ]
falpha.zk3.dec.com <Xm> [55] % workon -sb v32c mgo101106
cd'ing to sandbox source directory: /home/jennyd/sb/v32c/src.
starting new shell: /bin/csh.
falpha.zk3.dec.com <src> [31] % cd motif/lib/Xm
falpha.zk3.dec.com <Xm> [32] % srequest
This submit request will be logged against release 'v32csupport'
Is this correct ? [y]:
Enter the baselevel NUMBER [5]:
Is '[email protected]' your correct mailing address ? [y]:
Enter mail alias - must refer to one review committee:
ase_submit build_submit cde_submit
cluster_submit cmds_submit de_submit
etype_submit filesystem_submit habitat_submit
hardware_submit i18n_submit install_submit
kernel_submit ktools_submit lat_submit
mail_submit network_submit ootb_submit
print_submit proc_submit rt_submit
security_submit standards_submit svid_submit
sysman_submit threads_submit vm_submit
workstation_submit xdesktop_submit
[NO_DEFAULT]: workstation_submit
Enter aliases or usernames, in a comma separated list, to add to the
following cc mailing list for this submit request:
[email protected],osf_submit,[email protected],[email protected]
m,[email protected]
(enter a blank line to end) :
Press the return key to edit the list of files for this submit request:
./motif/lib/Xm/TextF.c
A bdiff log will be generated from the previous edited list of files.
You can include[i] the bdiff results in this form, specify the location[l]
of a file that contains previously generated bdiff's, or supply a pointer[p]
to place the newly generated bdiff's.
How do you want the bdiff's represented [i|l|p] : i
bstat'ing ./motif/lib/Xm/TextF.c
bdiff'ing ./motif/lib/Xm/TextF.c
*************************************************************************
************ Last Friday, I updated my srequest **********************
*************************************************************************
Fri Apr 26 12:15:22 EDT 1996
falpha.zk3.dec.com <DXm> [71] % workon -sb v32c mgo101106
cd'ing to sandbox source directory: /home/jennyd/sb/v32c/src.
starting new shell: /bin/csh.
falpha.zk3.dec.com <src> [31] % cd motif/lib/Xm
falpha.zk3.dec.com <Xm> [32] % srequest -update v32csupportx-13-jennyd
This submit request update will be logged against release 'v32csupport'
Is this correct ? [y]:
Enter the baselevel NUMBER [5]:
Update this form [y|n] ?: y
Submit request 'v32csupportx-13-jennyd' has been updated
******************************************************************************
********** I did a bsubmit TextF.c into v32c pool this morning, 4/29 ********
********** and get the following error. ********
******************************************************************************
falpha.zk3.dec.com <DXm> [86] % workon -sb v32c mgo101106
cd'ing to sandbox source directory: /home/jennyd/sb/v32c/src.
starting new shell: /bin/csh.
falpha.zk3.dec.com <src> [31] % cd motif/lib/Xm
falpha.zk3.dec.com <Xm> [32] % bstat TextF.c
[ ./motif/lib/Xm/TextF.c ]
[ There is no branch revison for set Jenny_Vu_mgo101106. ]
|
| Date Of Receipt: 3-MAY-1996 17:11:40.34
From: ALPHA::"[email protected]" "Joshua M. Friedman OSF/UNIX SDE"
To: jenny@locus_ode.wdec.locus.com
CC: [email protected]
Subj: Re: The same set name for different pools
Sorry:
> co error: Symbolic number V32SUPPORTOS is undefined.
> Where is V32SUPPORTOS defined?
I thought I'd gathered from your mail that you'd submitted to V32SUPPORTOS
already - that submit action creates the V32SUPPORTOS branch. If you've
submitted it to one pool, you can reference that pool with the -j as I
showed.
For additional help, please send to odehelp as I am going out of town for
a week.
-josh
---------
From jenny@locus_ode.wdec.locus.com Fri May 3 14:49:05 1996
Delivery-Date: Fri, 03 May 96 14:49:07 -0400
To: Joshua M. Friedman OSF/UNIX SDE <[email protected]>
Cc: jenny@locus_ode.wdec.locus.com
Subject: Re: The same set name for different pools
In-Reply-To: Your message of "Fri, 03 May 96 00:41:59 EDT."
<[email protected]>
Date: Fri, 03 May 96 14:48:59 -0400
From: "Jennifer D. Vu" <jenny@locus_ode.wdec.locus.com>
X-Mts: smtp
Joshua,
> Please check your sandbox src dir for .BCSset-* files and see if
>
> ODE saves your work on the RCS branch named for your set. You cannot
> use the same set in more than one sandbox for the same file (as you've
> found), though ODE doesn't currently block you (this has been bug-reported).
>
falpha.zk3.dec.com <src> [43] % ls .BCSset-*
.BCSset-Jenny_Vu_mgo101106
falpha.zk3.dec.com <src> [44] % more !$
more .BCSset-*
./motif/lib/Xm/TextF.c
> Yes, do a new bco/bci for the file in the other pools. You can do
> a "bco -jV32SUPPORTOS file" while backed to v32c and I believe you'll
> get exactly the version from the v32support pool; if this same exact
> version belongs in the other pools you can then bci/bsubmit.
>
I got the following error message when I did a bco -jV32SUPPORTOS TextF.c
falpha.zk3.dec.com <Xm> [46] % pwd
/share/alpha/usr/staff2/jennyd/sb/v32c/src/motif/lib/Xm
falpha.zk3.dec.com <Xm> [47] % bco -jV32SUPPORTOS TextF.c
[ ./motif/lib/Xm/TextF.c ]
co error: Symbolic number V32SUPPORTOS is undefined.
Where is V32SUPPORTOS defined?
Thanks,
Jenny
|