Re: Keeping last-modified dates

> >Again no. cp will update the timestamp for you.
> >It has the same bug :-)
>
> Yes, the Unix "cp" command works like that, but copying a file in,
> say, the Mac OS X Finder does preserve the modification date, which
> is what Mac users expect, since it's been that way for 22 years so
> far and shows no signs of changing. (I don't know how Windows behaves
> in this regard.)

I just wanted to point out that the timestamp problem does not exists
for make users. Their tools support them. If Mac Finder does not, then
they use something else on Mac. I think there is a POSIX cp for Mac.

Rebuild-all guys will start studying make when the build takes 2 hours
even on distcc net.

Another example besides cp that has both options is tar (tar --touch).
For tar keeping mtime is the default but it's a backup tool. Perhaps it
is the same with fsvs. (And then we arrived to other file metadata:
permissions.)

I think it's clear that keeping modification time is a useful option.
The question is which is the better default value. I think not keeping
is better even for Windows (if you can do anytime svn up --no-touch to
get the last edit time).

  WP

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Aug 30 15:26:35 2006