Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!samsung!munnari.oz.au!manuel!cmf851
From: cmf851@anu.oz.au (Albert Langer)
Newsgroups: comp.software-eng
Subject: Re: CVS-RCS
Message-ID: <1991May22.142240.16480@newshost.anu.edu.au>
Date: 22 May 91 14:22:40 GMT
References: <1991May21.135016.3671@apertus.uucp>
Sender: news@newshost.anu.edu.au
Organization: Computer Services Centre, Australian National University, Canberra, Australia.
Lines: 25

In article <1991May21.135016.3671@apertus.uucp> apertus!ivanp@tenfwd.uci.com writes:

>One can not check in a release, other than the most current. (cvs ci *)
>
>Is there a easy process that I am missing? 

I haven't actually used CVS yet, so this response may be quite wrong,
but from my reading of the docs there is indeed an easy process that you
are missing.

Try using cvs ci *

I think you will find that it checks in on the same branch that you
checked out on, since a record of what you checked out is kept in the
local admin files with your checked out source.

If I haven't misunderstood the essence of what cvs is all about, then
I suspect you have :-) and you need to re-read the docs free from any
preconceptions about how RCS and SCCS behave. If I'm wrong then I
need to do so myself and would welcome somebody pointing this out.


--
Opinions disclaimed (Authoritative answer from opinion server)
Header reply address wrong. Use cmf851@csc2.anu.edu.au