Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!emory!mephisto!mcnc!duke!juliet!khera
From: khera@juliet.cs.duke.edu (Vick Khera)
Newsgroups: comp.unix.questions
Subject: Re: RCS and multiple modules
Message-ID: <18035@duke.cs.duke.edu>
Date: 7 Mar 90 16:00:33 GMT
References: <22675@adm.BRL.MIL> <1990Mar6.195640.26473@agate.berkeley.edu>
Sender: news@duke.cs.duke.edu
Organization: Duke University CS Dept., Durham, NC 27706
Lines: 24

In article <1990Mar6.195640.26473@agate.berkeley.edu> ilan343@violet.berkeley.edu writes:
> [ ... ]
>I'd like to give it a revision name( or number in the X.XX.XX format).
>Also, I'd like use this name inside the code, as I can with keywords
>like $Header$ for each individual module.

Try using the RCS state.  this can be set with "rcs -s<state>:rev" and then
expanded in the source files with $State$.  you can also check out files
based on the state.  check out the man pages on rcs and co.

>I know of "symbolic names", but they seem somewhat inflexible. From
>what I understand, the symbolic names are associated to just the
>revision number itself, but not to the level number, or branches.
> [ ... ]

symbolic names refer to the revision *or* branch specified. check the man
page for rcs.  i do not believe you can get this information into the
source file, though.

							v.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Vick Khera                              Department of Computer Science
ARPA:   khera@cs.duke.edu               Duke University
UUCP:   ..!{mcnc,decvax}!duke!khera     Durham, NC 27706