Stefan Fuhrmann wrote:
> Stefan Küng wrote:
>
>> Stefan Fuhrmann wrote:
>>> Major: Fetching the WC status in Log and Revision graph dialogs
>>> actually performs a full WC scan (10+ Minutes at my office).
>>> I will look into this one.
>> For big wcs, there's a hidden registry key to prevent the full scan and
>> just scan the selected folder/file.
>>
>> HKCU\Software\TortoiseSVN\RecursiveLogRev
>
> Now that I had a look at the code, I wonder why we
> want to highlight the newest revision that can be
> found somewhere in the sub-tree. (For the rev graph
> this is different: there we are looking for modifications.)
>
> I can see the intend: user committed something
> /in/somewhere/deep/down and wants to see that
> on the WC root. However, that is wrong in the general
> case: node properties (merge info etc.), for instance,
> will not be up-to-date for parent folders. Also, earlier
> revisions may still create conflicts with local changes
> when the unsuspicious user updates to HEAD etc.
>
> IMHO, the only correct version to highlight is the commit
> revision of the respective WC node alone. In other words,
> RecursiveLogRev=2 should be the default.
The reason for crawling is that many projects have not many committers
(and many have only one). For those, they don't run update that often
and therefore the marked wc revision is always "wrong" because they know
that their wc is at HEAD but the log dialog does not indicate it.
Also, it's very unusual to update only subtrees. So if the crawl finds a
higher revision than the selected node, that's in most of all cases the
correct revision.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=1322782
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-03-14 19:00:33 CET