Jack Repenning wrote:
> At 11:52 AM +0200 8/6/03, SLOGEN wrote:
>>
>> http://host/path/to/repos/x/y;rev=5/z;rev=4
>>
>> Which retrieves the stuff that's named z, as it was in rev 4 of what
>> is named x/y on HEAD, as it was in rev 5's.
>>
>> Multiple ;rev='s would probably never be used, but they model the
>> exact possibilities that SVN offer, and in a _very_ sweet way!
>
> This sort of game is common in ClearCase, where a version is an
> attribute of an element, and the element has universal identity. But
> my poor brain can't quite figure out what it means in Subversion.
> You say "as it was in rev 5 of what is named x/y on HEAD" but that
> object may have had many versions in rev 4 -- one on each tag and
> branch.
>
> I think a Subversion version is only identified by the triple of:
> repo revision, path to the version of interest, and some unique
> identifier for what ClearCase calls the "element." What you've
> provided here doesn't quite reach that standard, does it? Which of
> the many versions present in revision 4 is wanted?
The one that has been copied to x/y/ in revision 5. Since subversion gives
each copy of a file a separate identifier (file revisions are identified by
a node id which is common to all copies and revisions of a file, a copy id
which is common to all revisions of a copy, and a revision number), this
should be possible to determine.
Having this type of url scheme would make it easier to support browsing of
copied/renamed files in ViewCVS (this currently doesn't work), even though
it isn't very intuitive IMO.
- Russ
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Aug 6 21:01:09 2003