*BSD News Article 43820


Return to BSD News archive

Xref: sserve comp.unix.bsd.misc:63 comp.unix.bsd.bsdi.misc:151 comp.unix.bsd.386bsd.misc:51
Newsgroups: comp.unix.bsd.misc,comp.unix.bsd.bsdi.misc,comp.unix.bsd.386bsd.misc
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.hawaii.edu!ames!usenet.hana.nm.kr!news.kreonet.re.kr!europa.chnt.gtegsc.com!news.umbc.edu!haven.umd.edu!purdue!news.bu.edu!news3.near.net!paperboy.wellfleet.com!news-feed-1.peachnet.edu!gatech!howland.reston.ans.net!news.sprintlink.net!redstone.interpath.net!sas!mozart.unx.sas.com!torpid.unx.sas.com!sastdr
From: sastdr@torpid.unx.sas.com (Thomas David Rivers)
Subject: Re: Help needed with RCS
Sender: news@unx.sas.com (Noter of Newsworthy Events)
Message-ID: <D7poyI.DJM@unx.sas.com>
Date: Thu, 27 Apr 1995 20:59:06 GMT
X-Nntp-Posting-Host: torpid.unx.sas.com
References: <3nonov$6vr@lo-fan.jpl.nasa.gov>
Organization: SAS Institute Inc.
Lines: 46

In article <3nonov$6vr@lo-fan.jpl.nasa.gov> oscar@jpl-devvax.jpl.nasa.gov (oscar) writes:
>I am trying to keep track or files used in both development and 
>test simultaneously.  The problem is checking in files for the
>test version and still being able check them out without knowing
>their exact rev number.  It seems that RCS does not provide an
>easy method of determining what branches exist off a trunk.
>
>I have versions 1.1, 1.2, 1.3, 2.1
>
>I want to test version 1 -- No problem extracting it using co -r1 *
>
>I need to modify the 1.3 file so I check it out with - co -l1 file
>and get the 1.3 version.
>
>I edit the file and check it back in using - ci -u file
>
>The file goes in with version 1.3.1.1
>
>Now i go to build a new test version using - co -r1 * and get the 1.3
>version of the file.
>
>How can I automatically get to the 1.3.1.1 version?
>
>
>
>Any other thougths, ideas, suggestions are very welcome
>
>Oscar.DeMartino@jpl.nasa.gov



 You usually accomplish this by using particular names; which you then
move along the branches.

 Then, instead of checking out based on -l1, you can check out
the particular named version (i.e. version1).

 So, in this case, the name "version1" would be associated with 1.3;
then, after making your change, you'd taken the "version1" name off
of 1.3 and put it on 1.3.1.1.

 The RCS man pages give the details about how to tag files with names.

	- Dave Rivers -
-- 
Yoiks and Away!