Lukas Reck wrote:
> Comparing the ctime would be more appropriate to determine if a file
> has been meddled with since the last update, wouldn't it?
No, it would not. The ctime is updated when the inode is modified, not
when the file's contents are changed. That means whenever you change
owner or permissions. The only reason ctime entered this discussion is
because it gets updated when you manually change the mtime ( to put it
back to where it was before you did modify the file ). The entire point
of not updating the mtime is to make it appear as though the file has
not been changed, for instance, when you restore the file from a backup.
Trying to second guess a manually overridden mtime by looking at the
ctime is not appropriate because it discards the user's wishes that they
expressed by modifying the mtime.
This is an error in the recode utility, not svn. Recode clearly
modifies the file, so it should not be trying to hide that fact by
reversing the mtime.
If recode doesn't have a way to disable this behavior, then an easy
workaround would be to touch the file when you recode.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Feb 19 21:09:38 2007