Les Mikesell wrote:
> 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.
And if you copy a file from one file system to another, what then? I
was under the impression from earlier discussion that Linux file
managers would create new files with new mtimes on copying, at least
in some circumstances?
- Anders
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-07-15 18:40:48 CEST