Re: Why does "svn diff" forbid "-rCOMMITTED"?

At 8:30 PM +0100 9/23/03, Julian Foad wrote:
>Ping!
>
>Anyone agree or disagree with this?
>
>- Julian
>
>>First, do we agree on the meaning of COMMITTED?
>>
>> COMMITTED: the newest revision in which the item was changed
>>before or at the BASE revision. (Therefore a working copy is
>>required. In fact the WC admin data includes the COMMITTED
>>revision number.) In particular, if the WC is not up to date then
>>COMMITTED does not mean the most recently revision of the item in
>>the repository.

Even firster: do we agree on the meaning of BASE?

While a WC is a very powerful way of identifying a particular version
of a file (versions of a bunch of files), I can easily conceive a URL
that also specifies enough info to identify an exact version of a
path; we've discussed that syntax endlessly here. Having located the
object in question, I can easily imagine wondering "when was this
actually changed last?". If you'll let me call that first one
"BASE", then I'll let you call that second one COMMITTED.

svn diff -r PREV:COMMITTED http://host/repo/trunk/dir/foo.c@3217

... may not be the official syntax for this, but I think it reads
naturally as "in revision 3217, find /trunk/dir/foo.c; then show the
latest change made to it."

-- 
-==-
Jack Repenning
CollabNet, Inc.
8000 Marina Boulevard, Suite 600
Brisbane, California 94005
o: 650.228.2562
c: 408.835-8090
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org