Excellent response, Graeme. To take it one step farther,
the lost information about modified time hurts
whenever the modified time is before the created time.
In both windows and *nix systems, the most common ways of
copying (mv, cp, move, copy, mouse-move, mouse-copy,
winzip, xcopy, etc.) ALL preserve the modified date
of the files.
The real question should not be "which tools use the modified
date", but "which tools do not use the modified date".
Therefore, consider the Use Case of versioning log files
(as opposed to source files). One would like to know
the modification date of the file because the file's
identity involves its last mod time. It would serve as
a welcome short cut to finding the correct file (like
a hash code) if svn would co the files with their
original mod dates.
Mike Brenner
Thompson, Graeme (AELE) wrote:
> This is also the case using the mv command between different disks,
> separate file systems - does not exist in the target file system,
> yet the mv command preserves the modified time.
>
> By your argument the modification time shoud be set to the time of the
> move.
Erik Huelsmann wrote:
>> Why? The file didn't exist in the target filesystem before
>> you checked it out...
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Feb 27 12:43:00 2007