[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | USG buildhelp questions/answers |
|
Moderator: | SMURF::FILTER |
|
Created: | Mon Apr 26 1993 |
Last Modified: | Mon Jan 20 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 2763 |
Total number of notes: | 5802 |
2319.0. "Re: one more time please" by AOSG::FILTER (Automatic Posting Software - mail to flume::puck) Wed May 29 1996 19:56
Date Of Receipt: 29-MAY-1996 17:56:53.93
From: FLUME::jmf "Joshua M. Friedman OSF/UNIX SDE"
To: [email protected]
CC: odehelp@DEC:.zko.flume
Subj: Re: one more time please
Charlie, srequest assumes you're in the set you want to use.
workon -sb sandboxname setname
is the way that you do a workon to a particular set, and then
you never need to use "-set setname" with bco or bsubmit and then
srequest will know the correct set.
This command:
bcs -u -o file
is how you outdate a file from the current set (and it removes all your
work for that file -- careful this may not be what you wanted!)
-josh
---------
To: [email protected]
Subject: one more time please
Date: Wed, 29 May 96 17:22:55 -0400
From: [email protected]
X-Mts: smtp
Status: R
When I check out a bunch of files that will later be submitted
together, then I think I'm supposed to use a 'set'
When I bco I should add -set CASENUMBER, then I'll be guaranteed
that when I bsubmit -set CASENUMBER that only those files will
be submitted. Of course if I check out more than when I finally
submit, I probably need to outdate the extra's somehow (please
include the method...)
Then the srequest can't doesn't appear to have a set option (or does
it ?). But the bsubmit will.
Please fill in any missing info.
thanks
Charlie
T.R | Title | User | Personal Name | Date | Lines
|
---|