[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: Steve Fairhead <steve_at_fivetrees.com>
Date: 2006-08-30 01:15:41 CEST

Ryan Schmidt said:
On Aug 29, 2006, at 22:25, Duncan Murdoch wrote:
> I would guess that it wouldn't be impossible to write wrapper scripts
> for svn that put the last mod date into a property just before a
> commit, and then modified the date based on that property just after a
> checkout or update. Tricky decisions would be what to do if an update
> resulted in a merge (presumably keep the merge time as last mod time),
> and recognizing cases where someone checked something in without using
> your script (so you'd need to fall back to the commit time).

The problem with that is obviously the initial import: If I'm importing a
project that's been developed without version control over the past two
years, I don't suddenly want all of the files in the project to have today's
(or any other) modification date. I want each file to remember the date on
which that file was modified. As has been explained by others, this is
useful information.


As a test, I've been doing just that, issue by issue, with an old, but still
on-going, project. Issue 1 was in May 1990. SVN doesn't know this.

The docs refer to SVN as being a file server with an added dimension: time.
Ironic, really ;).

(Lest I sound too harsh on this one point: I do appreciate the nature of
this enterprise, and value the work that's been put in. I'm just a kid with
a shiny new toy and a set of batteries that don't fit. Waaaah!)


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Aug 30 01:16:59 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.