On Tue, Jul 18, 2000 at 11:15:21AM -0700, Eric Chamberlain wrote:
> I have been under the understanding that a local file is considered
> "modified" only if its contents differ from the contents of the
> corresponding file in the repository. However, my experience with WinCVS
> client has been that if a file is regenerated with exactly the same source
> that it is marked as a modified file. In my particular case, I know that
> the file has not changed because it is mechanically produced.
How are you seeing it modified? If the date stamp is newer than the one
mentioned in the CVS directory, CVS doesn't know the file is really
unchanged until it sends the file to the server.
I will venture a guess that what WinCVS is seeing is something akin to a
cvs -n up. In that case, if you touch a file, cvs -n up will mark the file
as modified. But when you do a commit, it will then notice nothing is
done, and fix up the entry in the CVS directory.
On the other hand, why do you have a mechanically produced file in the
repository? Or, why isn't your build system erroneously rebuilding it?
(Though I think I did have similar problems with MSVC's *.dsp and/or *.dsw
files; been a while and can't remember).
mrc
--
Mike Castle Life is like a clock: You can work constantly
[EMAIL PROTECTED] and be right all the time, or not work at all
www.netcom.com/~dalgoda/ and be right at least twice a day. -- mrc
We are all of us living in the shadow of Manhattan. -- Watchmen
