Path: utzoo!attcan!uunet!lll-winken!ames!sun-barr!apple!motcsd!hpda!hpcupt1!hpirs!runyan
From: runyan@hpirs.HP.COM (Mark Runyan)
Newsgroups: comp.unix.questions
Subject: Re: RCS co/ci commands problem.
Message-ID: <4750018@hpirs.HP.COM>
Date: 9 May 89 17:54:19 GMT
References: <264@boake2.UUCP>
Organization: HP GSY/USO/UKL Cupertino, CA, USA
Lines: 21

>/ scott@boake2.UUCP (Scott Boake) /  7:13 pm  May  5, 1989 /
>
>Make changes to foo and do a 'ci -r1.1.1 foo'  No errors and a branch 1.1.1.1
>is now in the foo,v file.  I would prefer 1.1.1 but can live with the 1.1.1.1.
>
>Everything is just as I expected up to here.
>
>At this time I do a 'co foo' thinking I will get branch 1.1.1.1 - surprise!
>I have branch 1.1.

I suppose by this you are requesting that RCS should follow the top branch
out to the end of the branch.  I don't think you'll find an RCS that will
do that  (you may, I just don't know of one).

A possible solution is to use symbolic names and specify the revision you
want to check out.  For instance, you might call branch 1.1.1 release_1,
allowing you to use the command "co -rrelease_1 foo".  If you use this
symbolic name on all the files in the group, you may find it easier to
work with a group of files needed for "release_1" of the code.

Mark Runyan