Xref: utzoo comp.unix.questions:23012 comp.unix.wizards:22499
Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!umn-d-ub!cs.umn.edu!klein.geom.umn.edu!slevy
From: slevy@klein.geom.umn.edu (Stuart Levy)
Newsgroups: comp.unix.questions,comp.unix.wizards
Subject: Re: Question about RCS check-in
Keywords: RCS, ci, help
Message-ID: <1990Jun17.050747.27703@cs.umn.edu>
Date: 17 Jun 90 05:07:47 GMT
References: <558@fltk.UUCP>
Sender: news@cs.umn.edu (News administrator)
Distribution: usa
Organization: Geometry Group, University of Minnesota
Lines: 17

Yes.  The effect on 'make' of checking RCS'd files in/out really annoyed me.
I modified ci & co to optionally preserve the mod date: on checkin, to
(a) keep the source file modification date unchanged and (b) set the
RCS revision date = source file's mod date; on checkout, to set
checked-out file's mod date = RCS revision date.  Works great.

Walter Tichy argued this shouldn't be the default behavior, though;
if you have a source file on hand, then check out an older revision,
you'd *want* make to remake anything depending on that file.

It appears I'm not the only one to do this; Silicon Graphics' rcs package has
an option which does the same thing, just uses a different option letter (-M).

I can send source diffs (against RCS version 3 or 4) for the mods if you like.

	Stuart Levy, Geometry Group, University of Minnesota
	slevy@geom.umn.edu, (612) 624-1867