Re: Timestamp Issues

On Nov 29, 2004, at 8:40 PM, Tom Rawson wrote:

> Fair enough. The approach you described makes a lot of sense for a
> multiprogrammer C project. BUT the exact same requirement -- using
> timestamps to drive utilities that determine what files have been
> changed -- argues for the opposite approach when the code is not
> compiled and deployment uses the timestamps on the source code.

I agree with this. The option to preserve true modification time
should be available. (And preferrably built-in, not up to some wrapper
script hacking.)

Scott

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Nov 30 16:09:35 2004