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

Re: timestamp preservation design (issue 1256)

From: Justin Erenkrantz <justin_at_erenkrantz.com>
Date: 2003-06-24 01:05:10 CEST

--On Friday, June 20, 2003 9:33 AM -0700 Jack Repenning
<jrepenning@collab.net> wrote:

> Put another way: if you want vintages, use checkout. You're probably doing
> something like backup or export/import or audit or something else
> administrative, not developing, anyway. If you want to develop, then you
> desperately want your builds to do the right thing, and you can afford to
> sacrifice the "vintage" semantic to get that.

If we're going to do something re: timestamps, this would be the approach I'd
take. export and checkout get commit-time, and update gets current-time.

More precisely, if the file does not exist in the WC, it gets
last-commit-time, if it is patched, it gets current-time. This has the
advantage of playing nice with make(1). Any solution which opens a hole for
make figuring out whether a file has changed gets scorn from me. -- justin

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jun 24 01:05:54 2003

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

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