Attila Tajti wrote:
> Hey, I never said it's better than TSVN. It only had a feature I would like
> to have in TSVN as well. I never used it, I use TSVN for my projects so I
> didn't know abuot all these problems. The only thing I liked about Work
> was it's capability in showing tag/branch numbers in the log.
>> And after all this, I still haven't found what you're talking about.
>> The log dialog doesn't even show the changed files of each revision.
>> So where do you see branches/tags in the log dialog???
> See http://pysvn.tigris.org/docs/WorkBench.html
> You have to select "Update Project" menu item and fill in the tag and
> 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.
> Anyways thanks for your time for having a look at this. I must say that
> I tried Work Bench with only a test repository so I didn't know it was that
Try it: check out a working copy of Subversion and show the history for
> Thanks for the information, I didn't know that in some cases users have
> no access to the repository root. But I don't think that would be necessary
> as you can specify tag and branch url's and they don't have to access root.
> By the way, will revision graph work in this case?
I didn't know that either, but some people reported that the revision
graph didn't work for them. And that answers your question: no, the
revision graph won't work either in that case. But that's something I
can't do anything about: the revision graph needs the log from the
repository root, otherwise we have even less information and couldn't
draw a graph at all (even with that, the revision graph has to do a lot
of guessing because there's just not all information available which is
required for a reliable graph).
> I understand probably I wouldn't need a revision graph very often and
> most of the time a clean log would be enough, but I couldn't convince
> my co-workers and I wasn't that sure about it either. But basically every
> tag or branch of our repository could be represented by a revision number
> (which may not be true for every repository). I would like these numbers
> optionally cached and optionally see them in the log.
Well, Subversion just doesn't provide that kind of feature. And
implementing something like this (as Workbench does) just isn't a good
idea, because it puts a hell of a load on the server, is terribly slow
even for mediate repositories (I don't even want to try it on e.g. the
apr repository) and not even reliable (I could show you my test
repository - ok, maybe not a fair case because I do copies there a lot
and I don't have a real branches/tags/trunk layout, but still, it
doesn't work there).
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Mon Oct 3 22:04:44 2005