Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!lll-winken!ames!haven!mimsy!chris
From: chris@mimsy.UUCP (Chris Torek)
Newsgroups: comp.unix.wizards
Subject: Re: RCS
Message-ID: <16623@mimsy.UUCP>
Date: 30 Mar 89 00:07:55 GMT
References: <5372@lynx.UUCP>
Distribution: na
Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742
Lines: 31

In article <5372@lynx.UUCP> m5@lynx.uucp (Mike McNally) writes:
>When a file is checked out (with co) of an RCS directory, it seems to me
>that it would be nice if the modification date were set to the date of
>the revision.  This would keep "make" happy.

Since `co' expands RCS keywords, this would be wrong.  For instance:

	% co -l foo.c
	1.1 locked
	% edit foo.c
	...
	% make
	...
	% ./test foo
	works
	% ci foo.c
	...
	% co foo.c
	% make
	`foo' is up to date.
	% ident foo
	$Header: ... chris Locked $
	%

Other than the single `extra' recompilation (not always unnecessary,
as above), if you keep a copy co'd all the time, this is no problem.
Alternatively, you can use a variant of `make' that knows about RCS
files.
-- 
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163)
Domain:	chris@mimsy.umd.edu	Path:	uunet!mimsy!chris