Conference smurf::buildhelp

545.0. "Re: PREV_NAME are CURRENT_NAME in mkbranch script ..." by SMURF::FILTER (Automatic Posting Software - mail to flume::puck) Mon Jan 31 1994 15:57

Date Of Receipt: 	28-JAN-1994 16:37:59.51
From: 	US2RMC::"[email protected]" "Grant Van Dyck"
To: 	[email protected] (Rima Mansour 28-Jan-1994 1329)
CC: 	[email protected]
Subj: 	Re: PREV_NAME are CURRENT_NAME in mkbranch script ...

Thanks Rima,

I discovered this - as I ran it. I figured I'd just do what the man
page said and see what happened, and it did exactly that.

In my parfile:

UPTODATE_B=X11R6
CURRENT_NAME=x11r6

in the resultant RCS pool:

root@buffer [29] rlog -r FSGetCats.c,v

RCS file: FSGetCats.c,v
Working file: FSGetCats.c
head: 1.1
branch: 1.1
locks: strict
access list:
symbolic names:
        x11r6: 1.1.1.1
        X11R6: 1.1.1


	-Grant


| 
|   This is in response to Josh question regarding mkbranch:
|   BTW, I forgot the name of the person who will be
|   running mkbranch script, so I am sending my mail
|   to odehelp.
| 
|   PREV_NAME and CURRENT_NAME, are lower case
|   labels, tagged after the creation of the third party sources
|   on the new public branch, named by the value of
|   UPTODATE_B parameter.
| 
|   So, PREV_NAME are CURRENT_NAME need to be lower case,
|   since they don't represent a public branch.
| 
|   For further assistance, contact:
|  
|      mailing address: decwet::ode
|      tele#: (DTN)548-8709
| 
| thanks,
| /Rima
| 
| 
| 

% Received: 	by us2rmc.bb.dec.com; id AA12937; Fri, 28 Jan 94 16:35:23 -0500
	from localhost by cardinal.zk3.dec.com; (5.65/1.1.8.2/01Nov93-1038AM) id AA24957; Fri, 28 Jan 1994 16:37:52 -050
% Message-Id: 	<[email protected]>
% To: 	[email protected] (Rima Mansour 28-Jan-1994 1329)
% Cc: 	[email protected]
% Subject: 	Re: PREV_NAME are CURRENT_NAME in mkbranch script ...
% In-Reply-To: 	Your message of "Fri, 28 Jan 94 16:29:10 EST." <[email protected]>
% Date: 	Fri, 28 Jan 94 16:37:52 -0500
% From: 	Grant Van Dyck <[email protected]>
% X-Mts: 	smtp