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

Re: repobrowser fails to show directories that don't exist in HEAD when browing at older revision

From: Roel Harbers <roel_at_roelharbers.com>
Date: 2006-02-03 10:12:25 CET

Stefan Küng wrote:

> Roel Harbers wrote:
>>> Sure: As you can see in your own screenshot, the error message got
>>> copied as the URL of the repo browser to use. Since that URL isn't
>>> there, you'll get an error, and TSVN can't know what's the root of
>>> your repository, so every url part is treated as its own folder.
>> so.... why does the error message get put in the url box in the first
>> place? This may be purely cosmetic, but it looks a bit... odd. (Still
>> very happy with tsvn, don't get me wrong :P )
> You mean you didn't do that yourself?
> That means you have to provide me with a recipe on how to get the
> error message on a *folder* tree item - I only see error messages as
> file items, and those don't get copied to the URL of the repobrowser.
> So how did you do that?
> Stefan
I can only reproduce it when I start the repo browser from the merge dialog

to reproduce:

- start with a repository with default branches/tags/trunk structure,
let's say at revision 10
- delete a branch, let's say
http://server/repo/project/branches/tempbranch (r11)
- checkout the head of the trunk of the project
- select "merge..." from context menu of wc
- click top "..." button (select from repo browser)
- click the revision button in the repo browser, and select revision 10
- now go to http://server/repo/project/branches/tempbranch in the repo
browser. "Error * REPORT request failed on..." should appear
- click the error message. The error message is now appended to the url


Roel Harbers

To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Fri Feb 3 10:12:54 2006

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.