On Thu, Sep 06, 2001 at 01:02:07PM -0500, Ben Collins-Sussman wrote:
> Joe Orton <joe@manyfish.co.uk> writes:
>
> > In DeltaV a "baseline" records a snapshot of the version history of the
> > repository at some point in time. You can associate a "baseline
> > collection" with a baseline, which lets you look through that snapshot;
> > mod_dav_svn exposes a baseline collection for each revision of the SVN
> > repository. How's that sound?
>
> OK, this is about what I expected. In the world of CVS, a deltaV
> "baseline" might refer to a tagged collection of per-file RCS
> revisions. But in Subversion, each Revision tree is a baseline in
> itself.
>
> Hmmm, I wonder, then, why 'svn co -r 5' doesn't work over ra_dav. Is
> there just some code in there which always fetches the 'youngest'
> baseline, instead of baseline #5?
Okay...
ra_dav is doing a PROPFIND on /repos/svn/$svn/vcc/default asking for the
baseline-collection and version-name properties.
But in the response, mod_dav_svn is giving the properties for the URL
/repos/svn/$svn/bln/1, rather than /repos/svn/$svn/vcc/default.
<?xml version="1.0" encoding="utf-8"?>
<D:multistatus xmlns:D="DAV:">
<D:response xmlns:lp1="DAV:" xmlns:lp3="svn:">
<D:href>/repos/svn/$svn/bln/1</D:href>
### ^^^ should be /repos/svn/$svn/vcc/default???
<D:propstat>
<D:prop>
<lp1:baseline-collection><D:href>/repos/svn/$svn/bc/1/</D:href></lp1:baseline-collection>
<lp1:version-name>1</lp1:version-name>
</D:prop>
<D:status>HTTP/1.1 200 OK</D:status>
</D:propstat>
</D:response>
</D:multistatus>
My first guess would be to try and fix that...
joe
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:40 2006