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

Re: 1.6 release

From: Stefan Fuhrmann <stefanfuhrmann_at_alice-dsl.de>
Date: Sat, 14 Mar 2009 15:22:56 +0100

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.

-- Stefan^2.
Received on 2009-03-14 15:20:55 CET

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.