Anders J. Munch wrote:
>
>>> The "make argument" is flawed. Read my 2008-06-10 posting
>>> http://article.gmane.org/gmane.comp.version-control.subversion
>> .user/77803
>>
>> Sorry, this makes no sense. The whole idea of the last modified
>> timestamp is that it represents the time when this file was
>> last modified.
>
> Everyone agrees on that. The point of contention is whether moving
> identical file contents from one place to another constitutes
> modification.
>
> Or should I say, there are two different traditions, one that says it
> does, one that says it doesn't. Neither tradition is more right than
> the other, they are just different. And those who see a file as
> something that can be moved without changing it, would like to see
> Subversion support their tradition better.
If you are on a unix-like filesystem, you just use a different timestamp
for each purpose. mtime is for the last modification of the file
contents, ctime for inode changes like moves or ownership/permission
changes. Normally ctime can't be set by the user and can never be
earlier than mtime (because an update of mtime is an inode change that
triggers an update to ctime). Thus there is no doubt about what mtime
is supposed to mean, just a choice of which timestamp to observe for
your purpose.
--
Les Mikesell
lesmikesell_at_gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-07-15 14:50:21 CEST