On Sat, May 03, Greg Hudson wrote:
> On Sat, 2003-05-03 at 14:16, Alan Shutko wrote:
> > What version are you using? Checkouts have been setting the
> > timestamp appropriately for a while, though I don't know when,
> > offhand. I just tried it on my machine....
>
> I'm not sure how Michael Price got his result; in my experience, for a
> checkout or update, CVS sets the timestamp to the checkin date for a new
> file (which is all of the files in a checkout) or to the current time
> for a modified file. This produces no particularly useful guarantees.
>
> (And people do jump on CVS for its timestamp behavior. But solo turn is
> confusing the issue by conflating the timestamp a file gets on
> checkout/update/switch with the algorithm used to find changed files in
> a working directory.)
Well, the main issue remains. subversion must maintain the timestamps.
Maybe I have missed that part in the documentation how to set timestamp
related properties.
Using the commit time is not a very bad idea because that is the time
when other users of the repository have a chance to see the new data.
I'm not sure if subversion could do it better and use the real
modification time of the given file, that would make sense when one
imports his old stuff via 'svn add *'.
The current behaviour is broken. If this remains unchanged, document it
and explain the reasons behind this decision.
Gruss Olaf
--
USB is for mice, FireWire is for men!
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun May 4 22:36:25 2003