[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Keeping last-modified dates

From: Duncan Murdoch <murdoch_at_stats.uwo.ca>
Date: 2006-08-30 15:32:53 CEST

On 8/29/2006 6:52 PM, Ryan Schmidt wrote:
> On Aug 30, 2006, at 00:34, Gavin Lambert wrote:
>> For software source file control, at least, not preserving the
>> timestamps is definitely the way to go, as has already been explained
>> repeatedly. If you're using SVN for document versioning (which AFAIK
>> wasn't the original goal, but it's cool that it can be used that way)
>> then it *might* be desirable to preserve timestamps, if you don't
>> have a
>> better way of keeping track of documents. ('svn log' seems sufficient
>> to me.)
> Well, for *compiled* software projects using Makefiles or similar,
> Subversion's current behavior is useful. For me, it's not, as I write
> web sites in PHP, which is interpreted, not compiled. I don't use
> Makefiles.

I'm just curious: how does the current behaviour cause trouble in this
situation? In the only example I can think of (page reports "last
change" date) it seems to me that you really would want checkout or
update time shown, because that's when the page changed from the point
of view of someone using the web site. The developer can look at the
svn log to see when the page last changed in the repository.

Of course, this ignores the loss of information when importing an
existing project into svn; is that the main concern?

Duncan Murdoch

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:58:00 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.