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

RE: preserve modification date on co?

From: Walt Armour <WaltA_at_concur.com>
Date: 2004-09-09 22:33:51 CEST

> -----Original Message-----
> From: Lee Merrill [mailto:LeeMerrill@bustech.com]
> Sent: Thursday, September 09, 2004 1:26 PM
> Cc: users@subversion.tigris.org
> Subject: Re: preserve modification date on co?
> Hi everyone,
> But I think "check-in time" is virtually the same as modification
> time, though. The user could have modified the file 1 second before
> committing it, or 100 seconds, but I don't see why this
> history needs to
> be preserved. Especially for users checking out these changes, that
> history is unimportant, and "check-in time" is all that is needed, as
> far as I can tell.
> I'm not sure what you mean about modification time being
> beneficial in
> comparing files and directories, though, it seems diff is what you
> really want to use, and if the timestamps differ, it still
> doesn't matter...

I believe this was briefly mentioned in a previous post. In situations
where a generated file (generation conditional on source file modification
times) is also kept in SVN it would be very useful to have the file
timestamps be the actual modification times to facilitate proper generation
in later checkouts.

To be honest, this is the only situation I can think of where the timestamp
difference (modification versus commit) makes a difference. In every other
situation that comes to mind the file hasn't really been modified (as far as
the rest of the world is concerned) until it is committed.

We have one generated file that corresponds to this situation. We deal with
it using a specific commit/generate/commit sequence when it changes.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Sep 9 22:32:58 2004

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.