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

Re: Stop on copy can't be turned off in TSVN 1.5

From: J J <eggsgloriouseggs_at_gmail.com>
Date: Fri, 27 Jun 2008 11:22:40 -0500

>>>>>>> Hi,
>>>>>>> In TortoiseSVN 1.5 on Windows XP SP2 against a 1.5.0 server running
>>>>>>> on
>>>>>>> Solaris, if I right click on a branch and select Show Log, by default
>>>>>>> it comes up with "Stop on copy/rename" not selected and shows me all
>>>>>>> revisions follow the branches parents as I would expect. If I then
>>>>>>> select "Stop on copy/rename" it does the right thing and limits the
>>>>>>> revisions to only those on the branch. However when I deselect it
>>>>>>> again, it does not show all revisions again. I've tried hitting
>>>>>>> Refresh as well, but Stop on copy appears to still be effectively set
>>>>>>> even though the dialog shows it deselected.
>>>>>>> Is this a new bug? I didn't find anything searching the mailing
>>>>>>> lists. The issue tracker isn't responding for me, so I couldn't look
>>>>>>> there to see if a bug is already submitted.
>>>>>> Refresh in the log dialog only refreshes the messages which are
>>>>>> already
>>>>>> shown (otherwise it wouldn't be a refresh).
>>>>>> To get more log messages beyond the copy point, use the button "next
>>>>>> 100".
>>>>> This doesn't seem very intuitive. The revisions appeared by default
>>>>> and they automatically disappeared when selecting stop on copy. I
>>>>> would expect Next 100 to be required to get to the next 100 revisions,
>>>>> not the first 100.
>>>> And it will fetch the next 100 messages. As you would expect.
>>> Okay, I'll just make sure our users understand this. Thank you for your
>>> help.
>> One more thing... another reason why it is confusing is because when I
>> deselect it, all of the panes refresh as if they are incorporating my
>> change, but they return with the exact same content. Is there a
>> reason they refresh?
> Yes, it refreshes so it knows about where to stop. The functionality is
> implemented in the svn library, TSVN does not know where to stop (i.e.,
> where the copy point is).

That makes sense when I select it, but I don't understand why that
would be needed when deselecting. I would expect it to use 100
revisions if available. If not I don't understand why the refresh is
needed, which confuses users because the refresh seems to indicate
that it is doing something as a result of the deselect.

To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-06-27 18:22:47 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.