[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn commit: rev 617 - trunk/notes

From: Greg Stein <gstein_at_lyra.org>
Date: 2001-12-10 03:14:19 CET

On Fri, Dec 07, 2001 at 10:51:16AM -0600, Ben Collins-Sussman wrote:
> kfogel@tigris.org writes:
> > * STACK: In revision 596, Greg Stein meant to move STACK from the top
> > level to here, but only the delete succeeded -- the add never
> > happened (hmm). Anyway, here it is, albeit with no copy history.
>
> A quick note: you still could have re-added with history preserved.
> Just do a
>
> svn cp -r 595 http://..../STACK notes/
> svn ci
>
> In fact, this is the very feature you worked on last week, Karl. :-)

Yes, but have you *tried* the above command, Ben?

It doesn't work.

To reach the baseline collection for rev=595, it must ask for a properly
from the /trunk/STACK resource. That resource does not exist in the HEAD, so
it doesn't exist, so you can't ask for the property.

Oops :-)

I thought I had wrote a short email about this. Basically, get_baseline_info
is going to have to navigate up through parents when it gets 404 on
resources. Eventually, it would get to a parent that can get it over to the
baseline collection for the specified revision. Then it can compose the
baseline-relpath property with the set of components that it navigated to
give you a URL to the item in the BC.

I've got some ideas for optimizing the network traffic, but the upwards
navigation will be the first fix. A custom report (ugh) would also fix the
problem.

I just posted issue #581 for this.

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
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:52 2006

This is an archived mail posted to the Subversion Dev mailing list.