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

Re: [TSVN] tag history

From: Douglas Stonham <dstonham_at_pennysaverusa.net>
Date: 2005-10-03 22:38:41 CEST

On Mon, October 3, 2005 1:04 pm, Stefan Küng wrote:
> Attila Tajti wrote:
>> See http://pysvn.tigris.org/docs/WorkBench.html
>> You have to select "Update Project" menu item and fill in the tag and
>> branch
>> urls to build the tag/branch information.
> Ok, did that with my test Subversion working copy (the one where I work
> on implementing progress indication for GUI clients). When I choose
> "History...", it fetches the whole log from the repository root! With
> Subversion having > 16400 revisions, this is almost a crime - this is a
> very big load on the server for an operation that's usually done several
> times a day.

Just a thought you should feel free to shoot down (clay pigeon shooting
with feature requests?):

WorkBench apparently mangles the implementation but the basic idea doesn't
seem too bad... How about having two new properties, tsvn:tagurl and

If they aren't set, run the log and revision graph as normal. If they are
set, also grab the log for those two folders. Then interweave the log
entries into the log (with highlighted colours or something like that).

This certainly has limitations (those properties would only work for
projects with a definitive trunk/branch/tag structure and only from the
root of the trunk) but it would degrade nicely (nothing changes if they
are not set).

It sounds like it could get complicated for the log, but this would seem
to solve the problems you have mentioned with the revision graph not
having all the information it needs.

Hope that sounds good, sorry I don't have the expertise to tackle it myself.


To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Mon Oct 3 22:39:11 2005

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.