Conference smurf::buildhelp

1956.0. "two people/two sets/one srequest?" by AOSG::FILTER (Automatic Posting Software - mail to flume::puck) Fri Nov 17 1995 16:23

Date Of Receipt: 	17-NOV-1995 16:05:45.91
From: 	SMURF::QUARRY::devries "Mark DeVries sdt  17-Nov-1995 1603"
To: 	odehelp@DEC:.zko.quarry
CC: 	devries@DEC:.zko.quarry
Subj: 	two people/two sets/one srequest?

Bob Fontaine and I both work on libcurses.  We just got a new code drop from 
our supplier (Novell) and plan to provide the updated code for Pre-BL10.  We 
have to change about 200 files.  Here's our plan:

1) Each of us bco, edit, and bci about 100 files in our separate
   sandboxes.

2) Test.

3) Prepare one srequest when the time comes.  Manually concatenate the bstat
   output from our two sandboxes and include that in the single srequest.
   Post the huge diff files in a public directory and supply a pointer to
   that in the srequest.

4) Each of us perform one or more bsubmits to sign in the files, using the
   shared defect number.

Bob has in times past done multiple bsubmits on a single srequest that he 
created; in this case, however, two people with different sandbox working sets 
will be bsubmitting with the defect number that only one of them created.

Is that a problem?  Is anything above a problem (except for the sheer volume 
of files to keep track of)?  The good news is that there are about 350 files 
that we *don't* have to change.  :-)

Thanks,
Mark

Date Of Receipt: 	17-NOV-1995 16:16:16.77
From: 	SMURF::QUARRY::"[email protected]" "17-Nov-1995 1614"
To: 	[email protected]
CC: 	[email protected]
Subj: 	Re: two people/two sets/one srequest?

Mark,

	This sounds fine.  The defect id that srequest gives you is just used
	to track the changes that are submitted into the pool.  You should put
	in your submit request form all the parties involved in submitting the
	code is all.  When everyone gets ready to do their bsubmit just use
	the same defect id for each of the sandboxes.

Sean