[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: Robert Pluim <rpluim_at_bigfoot.com>
Date: 2003-06-24 10:09:45 CEST

Justin Erenkrantz writes:
> 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

What happens if I build at say rev X, update to rev A < X where a file
does not exist, then update to rev B < X where that file does exist?
If that file gets last-commit-time, make will not rebuild, even though
it should, which will cause whoever implemented it that way to be
tarred and feathered ;-)


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jun 24 10:05:22 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.