2009/6/6 Stefan Küng <tortoisesvn_at_gmail.com>:
> Mark Irving wrote:
>> (2) If I set RecursiveLogRev to 2 (because I have a large working
>> copy), I don't always see any revision highlighted for a folder. It
>> seems that this happens where the log messages for my working copy do
>> not include the exact revision to which it was updated: for example,
>> for a branch after a later commit has been made to the trunk.
>> Right-click folder, TortoiseSVN > Show Log. I see this at present,
>> for example, in a working copy of
>> http://svn.collab.net/repos/svn/branches/1.6.x -- and the behaviour
>> is different for show log of a file.
> the revision that's marked is taken from the (recursive if set in the
> registry) folder/file you right-clicked on to show the log. For files,
> that's the last committed revision.
>> (3) It might be nice if I could set the RecursiveLogRev behaviour for
>> each of my working copies. For big projects with thousands of files
>> and folders, I want RecursiveLogRev=2, but on small projects I would
>> prefer the default of RecursiveLogRev=1.
> On trunk, the status check to get the revision is done in a separate
> thread, so you shouldn't even notice it anymore even with big working
> copies - the log dialog automatically refreshes after the thread has
> finished and the revision is known. This means it won't first show the
> revision in bold until the thread is finished and the revision is known,
> but after that's done, the revision will change to bold.
I'm still a bit unclear on this. What happens if the registry key is
not defined (in 1.6.x and on trunk).
: oo // \\ "De Chelonian Mobile"
: (_,\/ \_/ \ TortoiseSVN
: \ \_/_\_/> The coolest Interface to (Sub)Version Control
: /_/ \_\ http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-06-06 12:49:29 CEST