Matthias Kranz wrote:
>
>
> ??? What do you mean with 'cvs diff' cannot detect that the file
> has changed. 'cvs diff' should show you the differences between
> two revisions of the same file. So if you copy subdir1/File1.hpp
> over dir1/File1.hpp
>
> 1. 'cvs status dir1/File1.hpp' should show you that the file is
> "Locally Modified".
>
This what I expect it to do, but ( I guess since the files have
the same timestamps ) the staus is "up to date"
> If you then commit this new version to the repository,
>
> 2. 'cvs diff -r 1.1 -r 1.2 dir1/File1.hpp' should produce an
> output with the differences between the two revisions.
>
I mean the simple case diffing my working version with the revision
that was checked out:
cvs diff dir1/File1.hpp
> If this is not what you mean or what you get, please provide the
> exact output of the commandline version.
>
I played and tested a little bit more - it seems to be caused by
the logic of cvs itself: it relies on filetimes. When I change the time
for dir1/File1.hpp everything works fine. As I noted, the
two files was committed exactly at the same time, and (I think this is
the problem) the revision dates of dir1/File1.hpp and
dir1/subdir1/File1.hpp are exactly the same. I remember a discussion
some weeks ago about using checksums instead of filetimes or in addition
to filetimes.
> Regards,
> Matthias
Regards,
Markus
--
COLOUR CONTROL Farbme�technik GmbH
Markus Niebel Bornaer Stra�e 205
mail: [EMAIL PROTECTED] D-09114 Chemnitz / Germany
