Conference smurf::buildhelp

451.0. "parallel bsubmits, re: need help with bsubmit" by SMURF::FILTER (Automatic Posting Software - mail to flume::puck) Tue Nov 30 1993 10:05

Date Of Receipt: 	23-NOV-1993 14:00:01.79
From: 	WASTED::jmf "Joshua M. Friedman ULTRIX SDE  23-Nov-1993 1359"
To: 	lueck@wasted:zko.dec
CC: 	odehelp@wasted:zko.dec
Subj: 	parallel bsubmits, re: need help with bsubmit

Greg, I assume (hope) that you have done these two sets of work in 
two different sandboxes, eg:
	workon -sb a
	bco / bci

	workon -sb b
	bco / bci

In which case you can just workon to the appropriate sandbox and submit,
if you later do a submit from the other sandbox, you'll encounter a merge
with your previous submit (which you can do outside of submit with 
bmerge -r$NEW).

If you have done both sets of work in either different sets or in the
same set in one sandbox, please let me know.  It sounds like you maybe
did:
	workon -sb a
	bco / bci	fix#1
	bco / bci	fix#2

In case, it's probably best to do the following - this assumes you've done
the bci of fix#2: 

	Save aside the current work
	    % cp file file.fix2
	Get the private file rev:
	    % bstat file
		(say you get #.#.#.3 - the final .3 is what matters)
	Outdate the last bci you did, using the final digit from bstat:
	    % bcs -o3 file

Now submit; when you're done, make sure you're backed to the submit tree,
and then immediately do a new bco, and assemble you're file.fix2 file
content with the current file header (or somehow manually merge the work),
then bci.

-josh

------- Forwarded Message

Return-Path: lueck 
Delivery-Date: Tue, 23 Nov 93 10:19:20 -0500
Return-Path: lueck
Received: from quarry.zk3.dec.com by flambe.zk3.dec.com; (5.65/1.1.8.2/01Nov93-1038AM)
	id AA16732; Tue, 23 Nov 1993 10:19:12 -0500
Received: by quarry.zk3.dec.com; id AA04457; Tue, 23 Nov 1993 10:18:26 -0500
Message-Id: <[email protected]>
To: odehelp
Cc: lueck
Subject: need help with bsubmit 
Date: Tue, 23 Nov 93 10:18:26 +28616
From: lueck
X-Mts: smtp


I have a question about using bsubmit in an unusual circumstance.

I made changes to a file for one bug, then sent them out to the FSRT for
review, and they were approved.  While that was happening, I made another
change to that same file.  I have also submitted this change the FSRT, but
it hasn't been approved yet.  Both changes are checked in separately to my
local tree.  I need a way to bsubmit the first change but not the second.

Is there a way to bsubmit a particular revision of a file?  The bsubmit
command does not seem to have a '-r' option.

Thanks for any help.

- -- Greg Lueck

------- End of Forwarded Message

Date Of Receipt: 	 6-JUN-1995 09:49:01.13
From: 	SMURF::WASTED::"[email protected]" "06-Jun-1995 0947"
To: 	[email protected]
CC: 	[email protected], [email protected]
Subj: 	bsubmits

	I have checked in (bci) the appropriate files and
need to submit the following:

 ../kernel/sys/table.h          ptos_1432_hms
 ../kernel/bsd/cmu_syscall.c    ptos_1432_hms

 ../kernel/ufs/mfs_vfsops.c	ptos_1467_hms


	The srequests were approved against the
BL5 tree.  However, I need to submit now, before
ptos_nightly closes.  I understand from F. Smith
this requires intervention by a 'root' user at
zk3.  Thanks.


			Humberto A. Sanchez II

Date Of Receipt: 	 6-JUN-1995 09:52:36.12
From: 	SMURF::FLUME::johnf "John Flanagan USG Test Johnf Tools Group  06-Jun-1995 0950"
To: 	[email protected]
CC: 	[email protected], [email protected], johnf@DEC:.zko.flume
Subj: 	Re: bsubmits

The 'root' intervention would be to add you to the bsubmit ACL file for
PTOS.  I checked, and you're already there, so you should be able to submit
anytime.

John


 ______________________________________________________________________

 John Flanagan	 		enet:    [email protected]	
 MS: ZKO3-3/W20			decnet:  flambe::johnf
 USG Release Engineering		 (603) 881-1719
 110 Spitbrook Road 			 (DTN) 381-1719
 Nashua, NH  
 ______________________________________________________________________