Steve Greenland wrote:
> On Thu, Feb 24, 2005 at 04:36:53PM -0500, Scott Palmer wrote:
> ...
>>I really don't understand, why argue against preserving valuable data?
>
> Because I don't think they are particularly valueable. And, in point of
> fact, I've not argued against subversion preserving it, only that it's
> of low value. Given choice between some working on preserving mod time
> vs., say, being able to do merge tracking, I know which one *I'd* vote
> for. (And I think you'd agree, based on your later comment.)
I just installed svn 2 days ago - now I realised that it does not
set the mod-time on checked-out files. :-(
Some experimenting showed that 'svn log -v' at least shows the dates
of the commits. I could live with it if the mod-time would be set to
this date, but this is also not done :-(
Is there a way to get it done, maybe by using "hook" or something
during checkout? I know several uses where having the mod-time at
least approximately right would be useful, e.g. 'll -tr' and so on,
therefore I would really love to have this feature.
>>>So preserving modtimes, at least on the import->checkout sequence,
>>>would be useful.
At least useful. IMHO.
>>Which side are you on? :)
>
> I'm on the side of useful features. I finally hit a situation where
> preservation of modtimes would be both useful and valid: protecting me
> from the autocrap tools. :-)
Whatever "autocrap tools" are, here is *my vote for* storing the
m-time of files during commit and restoring/setting the m-time during
checkout (and update, but only if the file changed)!
Have fun
Dirk
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Feb 25 17:44:51 2005