On Fri, 2006-01-13 at 09:27 -0600, Ben Collins-Sussman wrote:
> "[...]if you have DATE1:DATE2, that becomes REV1:REV2. That is way
> wrong, as that revision "range" might not really be all of the
> revisions between the dates, or REV2 could even be earlier than REV1,
> or some of the selected revisions might not be in the date range.
> DATE1:DATE2 should really map to {R1, R3, R14, R7, ...}. IOW, some
> ordered list of arbitrary revisions. The client is NOT set up for that
> at all, not to mention all the server and transport bits necessary to
> provide it."
Of course, even this is too simplistic. What does "svn diff -r
{1,3,14,7,...}" mean?
I like the semantics we have, even if they only work for linearly
date-ordered revisions. I think a repository with non-date-linear
revisions has no well-defined date semantics for the Subversion command
set; the dates on such a repository become descriptive metadata but not
indexable metadata, not as a trivial artifact of our implementation but
in a deeper, inherent sense.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jan 13 19:33:24 2006