On Tue, 2003-06-24 at 13:45, Ben Collins-Sussman wrote:
> 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?
The problem is that a checked-out directory will, more likely than not,
be updated. And if you show the commit times after a checkout, then
people (at least, the people who notice at all) will expect you to show
the commit times after an update, too. But we can't do that by default,
because that would break "make" even in the common cases.
Suppose there were some reason we couldn't implement the svn:executable
property at update time, but we could at checkout time. Would it make
sense to implement it anyway? No; it would be confusing and would only
hurt people.
On the other hand, an exported directory is never updated. So showing
the commit times in an exported directory does not create any bogus
expectations.
---------------------------------------------------------------------
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:58:00 2003