Path: utzoo!censor!isgtec!robert
From: robert@isgtec.UUCP (Robert Osborne)
Newsgroups: comp.software-eng
Subject: Re: CVS-RCS
Message-ID: <1076@isgtec.UUCP>
Date: 23 May 91 19:14:05 GMT
References: <1991May21.135016.3671@apertus.uucp>
Sender: news@isgtec.UUCP
Reply-To: robert@isgtec.UUCP
Lines: 22

In article <1991May21.135016.3671@apertus.uucp>, ivanp@mc.UUCP (Ivan Peters) writes:
|> How does CVS support (or does CVS support) dual derivations?
|> 
|> One can checkout a release.  (cvs co -rTEST1_0 test)
|> One can update from a release.    (cvs update -rTEST1_0 test)
|> 
|> One can not check in a release, other than the most current. (cvs ci *)

Hmmm, seems to be correct.  I think the only way to do this is either:
	1)  use rcs directly
	2)  use the checkin script
	3)  change 'cvs ci' so it takes the tag just like all the
		other commands  (ie. change the current argument -r to -F
		and -rTAG would check into the branch defined at that
		symbol)

I'll look into 3),  it might be fairly simple to do.  If Brian Berliner
is reading this maybe he has some input on this question, Brian?

Rob.
-- 
Robert A. Osborne   ...uunet!utai!lsuc!isgtec!robert or robert@isgtec.uucp