Xref: utzoo comp.unix.questions:23018 comp.unix.wizards:22504
Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uwm.edu!zaphod.mps.ohio-state.edu!usc!apple!voder!pyramid!unify!csusac!ucdavis!caldwr!rfinch
From: rfinch@caldwr.water.ca.gov (Ralph Finch)
Newsgroups: comp.unix.questions,comp.unix.wizards
Subject: Re: Question about RCS check-in
Keywords: RCS, ci, help
Message-ID: <186@locke.water.ca.gov>
Date: 16 Jun 90 16:59:52 GMT
References: <558@fltk.UUCP> <1990Jun16.011650.29099@virtech.uucp>
Followup-To: comp.unix.questions
Distribution: usa
Organization: Calif. Dept. of Water Resources, Sac.
Lines: 16

In article <1990Jun16.011650.29099@virtech.uucp> cpcahil@virtech.UUCP (Conor P. Cahill) writes:
>In article <558@fltk.UUCP> dnb@fltk.UUCP (David Buonomo) writes:
>>The problem is that the modification time on the source file changes when the
>>check-in occurs.

>The big question is "Why are you checking in source files that haven't 
>changed?"

He probably isn't.  Others have checked out the file, made changes,
and checked it back in.  The makefile detects that the ,v file has
changed and proceeds to check out his unchanged version again, and
recompile.  Does GNU make avoid this problem?
-- 
Ralph Finch			916-445-0088
rfinch@water.ca.gov		...ucbvax!ucdavis!caldwr!rfinch
Any opinions expressed are my own; they do not represent the DWR