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

Re: [TSVN] Stop on copy ticked but ignored. get 1st 100 logs.

From: Stefan Kng <tortoisesvn_at_gmail.com>
Date: 2006-06-11 09:56:09 CEST

Peter McNab wrote:

> I'm a little perplexed about the behavior of Log View in relation to the
> stop on copy checkbox.
> TSVN 1.4.0 rev 6666 (Hmm) (Win2k)
> After a commit from the CheckForModifications dialog ran Show Log, which
> listed log messages down to the first copy operation.
> (About 20 messages)
> The Stop on copy checkbox was ticked on form show.
> There is no "on-form" capability to re-extract the log messages from
> HEAD down to the first 100 just by un ticking the stop on copy check box
> and re-loading the log messages without exiting the Log View. (Maybe a
> useful feature to have)

Done in revision 6761.

> Unticked Stop on Copy.
> Closed Log View then re clicked Show Log from the commit dialog.

Hitting F5 would have been possible too.

> There was no change in the number of log messages displayed (about 20)
> and the Stop on Copy checkbox comes up ticked again.
> Show All does what is intended but I'm not keen on using that on a big
> repo.

How about 'next 100' ?

> Closed the dialogs.
> Used Right clicks to Show Log and it sucessfully produces the first 100
> messages including a number of (blue) copy log messages.
> Noted the Stop on Copy checkbox is still showing *ticked*. screenshot
> is attached.

Can't reproduce this. But I will pay more attention to this. If I ever
see it myself, I may be able to fix it.


   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 Sun Jun 11 09:56:23 2006

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.