Jim Blandy <jimb@red-bean.com> writes:
> the second number is guaranteed to be no greater than the first
> number. Thus the recent fix to the docs.
>
> However, in your conversation with Alexis Huxley, you pondered the
> possibility of changing this so that the second number might be
> greater than the first, if you passed `svn status' the `-u' flag, to
> allow it to consult the repository and see the latest revision.
This does touch on something important, though, I think:
The last-changed-rev is available *without* talking to the repository,
because it's recorded in the .svn/entries file:
<entry
committed-rev="2566"
name="Makefile.in"
text-time="2002-07-17T16:21:58.000000Z"
committed-date="2002-07-17T15:41:55.685214Z"
checksum="WMQuKeJsE1SjuP1yJtNBJA=="
last-author="sussman"
kind="file"
prop-time="2002-07-17T16:21:58.000000Z"/>
And "svn status -v" isn't the only thing that prints it; there's also
"svn info"...
But the main point is, since the information is local anyway, I think
it's safe to say that there will *always* be a way to get at it using
the command-line client. Probably we'd add a new column to the output
of "svn status -v" (rather than changing the meaning of the existing
column), but either way, there'll be plenty of warning, and it'll be
before 1.0.
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Jul 26 22:18:59 2002