Peter McNab wrote:
> Stefan Küng wrote:
>
>> On 12/16/05, Peter McNab <mcnab_p@melbpc.org.au> wrote:
>>
>>
>>> I notice the repo browser is pretty quick at showing the highest rev
>>> numbers on folders up the tree so would whatever method it uses suffice?
>>>
>>
>> It's not that the revision graph doesn't have the information about
>> the last committed revision. It's about how to extract that
>> information from the log, and then how to show it (how to connect with
>> which previous node).
>>
> Sorry for me being slow on the uptake but having extracted and
> interpreted the info to draw the graph, it might be sufficient to just
> show the latest rev number and not bother with another box and log message.
>
> So, in the tip of each node could it also include the highest rev number
> for that copy e.g. "Revision 232..243".
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
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Sat Dec 17 15:30:06 2005