Stefan Küng wrote:
>
> The biggest problem is to *extract* the information from the log info.
> It's not just as easy as doing an 'svn ls' or 'svn st -u' to find the
> last committed revision: items can have been deleted and don't exist
> anymore in HEAD, items can be renamed, moved, ...
> So it's not that easy to really find the last committed revision of
> all items reliably.
> Sure, it can be done, but it requires some time to implement (in a way
> that doesn't make the revision graph take 100% CPU for a minute
> because it's busy analyzing the data) and will then require even more
> time testing. That's why I put
> http://tortoisesvn.berlios.de/issues/?do=details&id=192
> to 1.4 and not 1.3.
>
> Stefan
>
Thanks for that.
I misunderstood your prior post on this matter and at the same time had
that "brilliant" idea about showing the extra rev numbers in the
existing tips. I'm perplexed though because the repo browser doesn't
show much of a delay when new paths are browsed into, which is where my
assumption that that updating the graph should not be slow.
Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Sat Dec 17 16:07:43 2005