Re: timestamp preservation design (issue 1256)

Greg Hudson <ghudson@MIT.EDU> writes:
>
> > * checkouts and updates always use the commit-time
> >
> > * updates always use the 'now' time.
> >
> > This allows 'make' to work no matter what, even if you do unusual wc
> > backdating that involves deletes & adds. Is that a 100% solution?
>
> I think you meant to say "checkouts and exports."

Yes, sorry, dumb typo.

> I think that solution is 100% make-compliant, but I don't see how
> changing the checkout behavior helps anyone.

It helps for the same reason that it's useful in an export. Somebody
checks out a fresh tree... it's interesting for the timestamps to
intially show how "old" each file is.

I'm not sure how to debate this point: is there an 'objective' way to
prove that a fresh checkout [is|isn't] surprising if it has
[commit-time|now-time] timestamps?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jun 24 21:47:35 2003