Re: Poor performance in windows. Switching back to CVS

Jan Hendrik wrote:
>> As far as I see, "something that makes a
>> modification without changing the timestamp" would only do it for the
>> reason that it thinks that is the correct timestamp. And yes, those
>> tools are a threat.
>
> Really? At least "touch" did not originate in Redmond, but in
> praised *nix.

Note that on *nix and similar systems there are 3 timestamps per file.
One relates to the file modifications (mtime) and can be set by user
applications, permitting existing times to be maintained for copies or
the time to be set artificially by touch. However the inode-change
timestamp (ctime) is always set automatically by the system when any
other change happens, including things like a rename, ownership,
permissions or the modification of the mtime timestamp. For things like
backups where you want to catch any kind of change, you should always
use the ctime timestamp. Some filesystems now allow the ctime
timestamp to be manipulated as well, but the original scheme did not.

-- 
   Les Mikesell
    lesmikesell@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org