Conference smurf::buildhelp

115.0. "reporting bugs on bsubmit, re: input on bsubmit problem from Ron" by SMURF::FILTER (Automatic Posting Software - mail to flume::puck) Mon Jun 07 1993 18:20

Date Of Receipt: 	 4-JUN-1993 20:01:30.73
From: 	WASTED::jmf "Joshua M. Friedman ULTRIX SDE  04-Jun-1993 2002"
To: 	[email protected], [email protected]
CC: 	odehelp@wasted:zko.dec, [email protected], [email protected],
	tresvik@wasted:zko.dec
Subj: 	reporting bugs on bsubmit, re: input on bsubmit problem from Ron

Ron and Larry,

Each of you, please, in your sandbox where the problems occurred (if
the sandboxes are still around, else in another sandbox), type gen-ptt,
and fill out and mail the bug report submission form (it does this for
you if your machine is setup to send mail).  You need to supply and
Abstract in the form where indicated, and the problem description.

Please provide as much detail as you can muster about what you were
doing, what happened, how you got there (eg. did you do just a straight
bco, edit, bci, bsubmit  with all the defaults, or did you do anything
to interrupt this flow or out of the norm).  Especially important are
any steps you took to customize your environment, rc_files, .BCS files,
or any steps to override any defaults (such as the 'rco' options mentioned).

We don't, in general, report bugs for others unless the problem is
reproduceable in our environment.

If you need help with gen-ptt I'll be glad to assist you.

Note that if you plan to type "rco" at the submit merge menu, and type
"co" instead, this will result in your choosing to throw out your
changes.  This sort of typo might be easy to do, and could account for
the problem you've seen.  I do plan to ptt report this "co" option as
one that should catch the user with a warning that changes are about to
be lost, requiring confirmation, with a default of "no",

thanks...		-josh


------- Forwarded Message

Return-Path: [email protected]
Received: by abyss.zk3.dec.com (5.65/DEC-USSG-ZK3-ULTRIX-09/27/91);
	id AA03058; Fri, 4 Jun 1993 17:09:36 -0400
Date: Fri, 4 Jun 1993 17:09:36 -0400
From: [email protected] (Heather Gray )
Message-Id: <[email protected]>
To: [email protected]
Subject: input on bsubmit problem from Ron
Cc: [email protected], [email protected], [email protected],
        [email protected]

Josh,
    The piece attached below was provided by Ron Menner. 

Larry, 
Josh was asking for some more information on the bsubmit
problems that had been experienced.  If there's anything
you can help with, please let Josh know.  He suggested
2 possibilities that could affect this: specifying the 'co'
option instead of 'rco', or doing some sort of re-targetting.
Any recollection?

thanks,
Heather
- ----------------

>>    2. bsubmit indicating no merge action was required by the
>>          submittor, and yet the resultant file in the pool being 
>>          "not what I bsubmitted"
>>          - 3 (known!) files

This happened to me also.  For the Streams submit we were basicly
doing a replace since we had already merged our files the day before.
At the bmerge prompt for edit, "rco" was being entered to overwrite
what was currently in the pool.  But on one occasion a file showed
up as requiring merge action but instead of asking the bmerge edit
question it gave the bmerge "ok" prompt.  Since muliple files were
being submitted at once and the bmerge "ok" prompt does not contain
the file name ... i mistakenly thought it was prompting again for
the same file that i already had responded "ok" to.  Once this file
was submitted it showed up as no merge conflicts to a subsequent
submit.



------- End of Forwarded Message

Date Of Receipt: 	26-SEP-1994 09:47:43.96
From: 	FLAMBE::johnf "John Flanagan USG Test Johnf Tools Group  26-Sep-1994 0944"
To: 	"[email protected]" <lmiller@DEC:.zko.flambe>
CC: 	odehelp@DEC:.zko.flambe, metsky@DEC:.zko.flambe
Subj: 	Re: ptos srequest

The srequest form for Platinum is still under review.  What I would do is
fill out a preliminary form using the Gold Minor form.  I know that the 
Platinum team is going to be asking some slightly different questions on
the form, so they will probably want you to redo the srequest once the new
form is in place.

You might want to check with Mark Warren, the Platinum T.L. to see what he
wants you to do.

John